From mev at tid.es Tue Oct 1 12:08:35 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 01 Oct 2013 10:08:35 +0000 Subject: [Fiware-wpl] Agile dynamic - release and sprint closing -> request for cooperation Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890B3627@EX10-MB2-MAD.hi.inet> Dear Partners, Find linked the dashboards produced to capture the release and sprint closing. https://forge.fi-ware.eu/docman/view.php/27/2859/FIWARE.backlog.apps.dashboard.20130930-1802.xlsx https://forge.fi-ware.eu/docman/view.php/27/2860/FIWARE.backlog.cloud.dashboard.20130930-1802.xlsx https://forge.fi-ware.eu/docman/view.php/27/2863/FIWARE.backlog.iot.dashboard.20130930-1803.xlsx https://forge.fi-ware.eu/docman/view.php/27/2861/FIWARE.backlog.data.dashboard.20130930-1802.xlsx https://forge.fi-ware.eu/docman/view.php/27/2862/FIWARE.backlog.i2nd.dashboard.20130930-1802.xlsx https://forge.fi-ware.eu/docman/view.php/27/2864/FIWARE.backlog.security.dashboard.20130930-1803.xlsx After having a look at the burndown diagrams mainly, which show how items were closed over time, I see many GEi onwers didn't perform any action to close the release or sprint. I'd need to know the reasons preventing those GEi onwers to close their items properly. In general I think we need to come to the right agile dynamic as soon as possible. I can also appreciate that some GEi owners in the following chapters Data, Security and I2ND did close the corresponding items properly, what I thank them for. The agile methodology gives flexibility when you set up your backlog, it means at the sprint planning. Afterwards, it needs us to be diligent and keep committed to the backlog. I wonder whether any of you had a chance to pay attention to the review report from the EC and read the comments related to the backlog. I'll be following the agile dynamic closely so as to demonstrate the EC that FI-WARE is working properly. In these regards, next backlog deliverable may be structured on a GE Implementation bases with views of your burn down and flow charts. In general, following the agile dynamic I think it's a shared objective, so I need to ask for your cooperation to overcome the current situation. I'm also requesting the Work Package Leaders to include in your weekly agendas a time slot for backlog maintenance. Thanks in advance for cooperation!! If anything, please, don't hesitate to let me know. Kind regards Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Tue Oct 1 15:48:24 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 1 Oct 2013 13:48:24 +0000 Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE In-Reply-To: References: Message-ID: <393554EDCF801348BC53C7813C6CB73B19CAB1C5@DEWDFEMB14A.global.corp.sap> Hi Juan, all, BTW do you or Juanjo have a statistics how many FI-WARE partners have indeed sent individual exploitation plans to EC after their first request immediately after the review? I am not sure if something about this is mentioned in the report who did or who did not, do you know? Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Montag, 30. September 2013 15:59 To: Juan Bare?o Guerenabarrena; jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Dear All We can summary the previous mail with the Recommendation 12, see below, so it is clear that they demand new confidential individual exploitation plans, but we have to confirm that this replaces the 11.2.2 resubmission, as they mentioned before in the Outcome document. Recommendation 12 (Page 12- FI WARE Review 5 Report) Provide a credible and precise exploitation plan for each partner who provides a GE implementation. Such information was orally requested by the European Commission Project Officer at the end of the Month 24 Review Meeting. The information must be submitted before the end of October 2013. It may be submitted by the partner concerned on a confidential basis to the European Commission Project Officer. It is expected that the exploitation plans will cover all GE implementations to a sufficient degree demonstrating business commitment. [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: lunes, 30 de septiembre de 2013 15:26 To: jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Hi Juanjo Please find here enclosed the main comments on the exploitation side by the reviewers. In the first document about the Outcome, I have doubts about what exactly we have to provide (see paragraph in red), exploitation plans by GE implementation of each owner?? In each individual exploitation plan define the exploitation plans by GE implementation??...notes that they said that the resubmission of D11.2.2 is replaced by this request for confidential plans, so resubmission for D11.2.2 is not necessary??.........but for sure we all have to work in a new and agreed version for next year review or we have to resubmit D11.2.2, right now, with the strategic vision we shared in the review properly included? I enclosed you also the feedback on the individual exploitation plans form the FI WARE Review Report, I will come back with additional comments regarding exploitation an Action Plan needed, but first it is important to Know what exactly we have to provide by 31 October 2013, regarding exploitation Thanks for your support Juan - 1_ Outcome FI WARE Review: (Page 3): Therefore, the Commission requests exploitation plans: o For all GE implementations except the 16 above-mentioned GE implementations with open source software licenses, so for the 32 and other GE implementations that are not (yet) in the Catalogue. The cockpit contains several of those. o To be provided by the GE implementation owner, irrespective of the type of organization, so commercial or not. Organizations that joined the consortium as a result of a competitive call for additional beneficiaries and their GE implementations are excluded. o To be sent directly to the Commission. o To be provided before 31 October 2013. In case no document is received by that date, the latest available version will be used, i.e. deliverable D11.2.2 or individual exploitation plans sent to the Commission after the last review meeting (the confidential ones). o To be provided instead of the requested resubmission of deliverable D11.2.2. The review report requests a resubmission of D11.2.2 for month 30 . This is replaced by this request for confidential, individual exploitation plans. The received or latest exploitation plans will be evaluated. Use of the respective GE implementations by the phase 2 use case projects will also be considered. The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project. - 2_ FI WARE Review 5 Report: o Pag 4. In line with the above requested: Exploitation of project results by FI-WARE partners ? The (lack of) substance and concreteness for the vast majority of the individual exploitation plans, at Month 24, is totally inappropriate for the ambition of FI-WARE and incommensurate with the claimed business commitment to project results by the main partners, even to Vice-President Kroes. As for the previous period, there is no visible attempt to echo - let alone apply - the well-elaborated business and ecosystem analysis to the individual partners' own approach and planning regarding project results. The reviewers are exceedingly concerned about the dearth of concrete evidence of the business commitment of GE implementation owners, and the corresponding lack of concrete information and traceability of GE implementations in the exploitation plans of these owners. - (Page 50)- Feedback regarding Individual Exploitation plans: D11.2.2 Exploitation Plan, including IPR Management o Unfortunately, despite the repeated comments by the reviewers on this very subject, the specific company exploitation plans are still generic and in some cases bordering on being a "wish list". They all say positive things but lack specificity in themes, markets, applications, timeline, budget and resources dedicated to the success of FI-WARE. With a few exceptions such as those supplied by ATOS and Thales and to some extent Telefonica and France Telecom, the individual exploitation plans are largely a collection of wishes, expectations and high level aims o In all cases, there are surprisingly very few references to specific GEs (or GE combinations) even by the owners concerned. In addition, they are a collation of single plans without any attempt to explain which type of synchronisation or coordination will happen among them and how this concerted effort will be coordinated, if any. There is not a single reference in the individual plans to the OIL, which is positioned in the generic part of the document as a key vehicle to "pave the way for a successful exploitation and sustainability of its [the FI-WARE project] results". [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: jueves, 26 de septiembre de 2013 15:33 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: FI-WARE - Outcome Letter & Review report Dear FI-WARE partners, Please find enclosed the report of the last review meeting. I haven't had time to review it in detail, just a very quick reading of the summary sections. Overall, I'm satisfied with the results and I tend to agree with some of the points about which the review establish we should implement remedies: * Improvement of the backlog management (this has led to rejection of the backlog deliverables and, most probably, the rejection of the Technical Roadmap deliverable). * Deep and carefully revision of contents in the FI-WARE Catalogue, overall regarding the all which has to do with terms and conditions of usage beyond the FI-PPP * Re-submission of Security Open Specifications. Apparently (at least considering those pieces I have read) this has to do with the IdM GE Open Specifications, so the good news is that we are already working to solve this issue. More kind of a surprise to me is the rejection of the following deliverables: * Deliverables linked the Tools chapter. * Report on validation by Use Case projects. * Exploitation Plan (given the fact that the consortium deliverable may be not satisfactory enough, but I was hoping that the individual exploitation plans shared in confidentiality with the EC had been more convincing ...) We will need to read the review more carefully to understand the reasons why those deliverables have been rejected. On the other hand, I'm happy to see that most of the chapter technical deliverables have been accepted. Unfortunately, the review could not incorporate results of the successful launch of FI-LAB at the Campus Party Europe event, because this took place after the review meeting. If so, I'm pretty sure that the analysis had been more favorable. This is a very raw analysis. Please don't consider it complete. We need more time to digest the whole report. Let's make a more close analysis and come back with a detailed action plan. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE - Outcome Letter & Review report Date: Thu, 26 Sep 2013 12:56:19 +0000 From: To: CC: , , , , , , , Dear Mr Hierro, Please find attached a copy of the outcome letter and review report of project 285248 FI-WARE. Please acknowledge receipt of this letter. Many thanks in advance Best regards, Vanessa Vanhumbeeck European Commission DG CONNECT Unit E3 - Net Innovation Tel.: +32 2 296 49 39 Email: vanessa.vanhumbeeck at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: From juan.bareno at atos.net Tue Oct 1 15:58:54 2013 From: juan.bareno at atos.net (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Tue, 1 Oct 2013 15:58:54 +0200 Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE In-Reply-To: <393554EDCF801348BC53C7813C6CB73B19CAB1C5@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B19CAB1C5@DEWDFEMB14A.global.corp.sap> Message-ID: Hi Markus Please find the list, regarding new confidential exploitation plans delivered after the review, below: o TID- Delivered o SAP- Delivered without any modification o IBM- No news o FT- No news o DT- No news o TI- Delivered o THALES- No news o ENG- No news o INTEL- Delivered o Atos- Delivered without any modification o SIEMENS- Delivered o NOKIA SIEMENS NETWORKS- No news o ALCATEL- Delivered o TECHNICOLOR- Delivered o NEC- Delivered Br Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: Heller, Markus [mailto:markus.heller at sap.com] Sent: martes, 01 de octubre de 2013 15:48 To: Juan Bare?o Guerenabarrena Cc: fiware-wpl at lists.fi-ware.eu; jhierro at tid.es Subject: RE: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE Hi Juan, all, BTW do you or Juanjo have a statistics how many FI-WARE partners have indeed sent individual exploitation plans to EC after their first request immediately after the review? I am not sure if something about this is mentioned in the report who did or who did not, do you know? Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Montag, 30. September 2013 15:59 To: Juan Bare?o Guerenabarrena; jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Dear All We can summary the previous mail with the Recommendation 12, see below, so it is clear that they demand new confidential individual exploitation plans, but we have to confirm that this replaces the 11.2.2 resubmission, as they mentioned before in the Outcome document. Recommendation 12 (Page 12- FI WARE Review 5 Report) Provide a credible and precise exploitation plan for each partner who provides a GE implementation. Such information was orally requested by the European Commission Project Officer at the end of the Month 24 Review Meeting. The information must be submitted before the end of October 2013. It may be submitted by the partner concerned on a confidential basis to the European Commission Project Officer. It is expected that the exploitation plans will cover all GE implementations to a sufficient degree demonstrating business commitment. Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: lunes, 30 de septiembre de 2013 15:26 To: jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Hi Juanjo Please find here enclosed the main comments on the exploitation side by the reviewers. In the first document about the Outcome, I have doubts about what exactly we have to provide (see paragraph in red), exploitation plans by GE implementation of each owner?? In each individual exploitation plan define the exploitation plans by GE implementation??...notes that they said that the resubmission of D11.2.2 is replaced by this request for confidential plans, so resubmission for D11.2.2 is not necessary??.........but for sure we all have to work in a new and agreed version for next year review or we have to resubmit D11.2.2, right now, with the strategic vision we shared in the review properly included? I enclosed you also the feedback on the individual exploitation plans form the FI WARE Review Report, I will come back with additional comments regarding exploitation an Action Plan needed, but first it is important to Know what exactly we have to provide by 31 October 2013, regarding exploitation Thanks for your support Juan - 1_ Outcome FI WARE Review: (Page 3): Therefore, the Commission requests exploitation plans: o For all GE implementations except the 16 above-mentioned GE implementations with open source software licenses, so for the 32 and other GE implementations that are not (yet) in the Catalogue. The cockpit contains several of those. o To be provided by the GE implementation owner, irrespective of the type of organization, so commercial or not. Organizations that joined the consortium as a result of a competitive call for additional beneficiaries and their GE implementations are excluded. o To be sent directly to the Commission. o To be provided before 31 October 2013. In case no document is received by that date, the latest available version will be used, i.e. deliverable D11.2.2 or individual exploitation plans sent to the Commission after the last review meeting (the confidential ones). o To be provided instead of the requested resubmission of deliverable D11.2.2. The review report requests a resubmission of D11.2.2 for month 30 . This is replaced by this request for confidential, individual exploitation plans. The received or latest exploitation plans will be evaluated. Use of the respective GE implementations by the phase 2 use case projects will also be considered. The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project. - 2_ FI WARE Review 5 Report: o Pag 4. In line with the above requested: Exploitation of project results by FI-WARE partners ? The (lack of) substance and concreteness for the vast majority of the individual exploitation plans, at Month 24, is totally inappropriate for the ambition of FI-WARE and incommensurate with the claimed business commitment to project results by the main partners, even to Vice-President Kroes. As for the previous period, there is no visible attempt to echo - let alone apply - the well-elaborated business and ecosystem analysis to the individual partners' own approach and planning regarding project results. The reviewers are exceedingly concerned about the dearth of concrete evidence of the business commitment of GE implementation owners, and the corresponding lack of concrete information and traceability of GE implementations in the exploitation plans of these owners. - (Page 50)- Feedback regarding Individual Exploitation plans: D11.2.2 Exploitation Plan, including IPR Management o Unfortunately, despite the repeated comments by the reviewers on this very subject, the specific company exploitation plans are still generic and in some cases bordering on being a "wish list". They all say positive things but lack specificity in themes, markets, applications, timeline, budget and resources dedicated to the success of FI-WARE. With a few exceptions such as those supplied by ATOS and Thales and to some extent Telefonica and France Telecom, the individual exploitation plans are largely a collection of wishes, expectations and high level aims o In all cases, there are surprisingly very few references to specific GEs (or GE combinations) even by the owners concerned. In addition, they are a collation of single plans without any attempt to explain which type of synchronisation or coordination will happen among them and how this concerted effort will be coordinated, if any. There is not a single reference in the individual plans to the OIL, which is positioned in the generic part of the document as a key vehicle to "pave the way for a successful exploitation and sustainability of its [the FI-WARE project] results". Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: jueves, 26 de septiembre de 2013 15:33 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: FI-WARE - Outcome Letter & Review report Dear FI-WARE partners, Please find enclosed the report of the last review meeting. I haven't had time to review it in detail, just a very quick reading of the summary sections. Overall, I'm satisfied with the results and I tend to agree with some of the points about which the review establish we should implement remedies: * Improvement of the backlog management (this has led to rejection of the backlog deliverables and, most probably, the rejection of the Technical Roadmap deliverable). * Deep and carefully revision of contents in the FI-WARE Catalogue, overall regarding the all which has to do with terms and conditions of usage beyond the FI-PPP * Re-submission of Security Open Specifications. Apparently (at least considering those pieces I have read) this has to do with the IdM GE Open Specifications, so the good news is that we are already working to solve this issue. More kind of a surprise to me is the rejection of the following deliverables: * Deliverables linked the Tools chapter. * Report on validation by Use Case projects. * Exploitation Plan (given the fact that the consortium deliverable may be not satisfactory enough, but I was hoping that the individual exploitation plans shared in confidentiality with the EC had been more convincing ...) We will need to read the review more carefully to understand the reasons why those deliverables have been rejected. On the other hand, I'm happy to see that most of the chapter technical deliverables have been accepted. Unfortunately, the review could not incorporate results of the successful launch of FI-LAB at the Campus Party Europe event, because this took place after the review meeting. If so, I'm pretty sure that the analysis had been more favorable. This is a very raw analysis. Please don't consider it complete. We need more time to digest the whole report. Let's make a more close analysis and come back with a detailed action plan. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE - Outcome Letter & Review report Date: Thu, 26 Sep 2013 12:56:19 +0000 From: To: CC: , , , , , , , Dear Mr Hierro, Please find attached a copy of the outcome letter and review report of project 285248 FI-WARE. Please acknowledge receipt of this letter. Many thanks in advance Best regards, Vanessa Vanhumbeeck European Commission DG CONNECT Unit E3 - Net Innovation Tel.: +32 2 296 49 39 Email: vanessa.vanhumbeeck at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: From pascal.bisson at thalesgroup.com Tue Oct 1 17:31:32 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 1 Oct 2013 17:31:32 +0200 Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE In-Reply-To: References: <393554EDCF801348BC53C7813C6CB73B19CAB1C5@DEWDFEMB14A.global.corp.sap> Message-ID: <4112_1380641499_524AEADB_4112_622_3_fd2a0649-d35e-4aea-be01-58d130c0b041@THSONEA01HUB05P.one.grp> Dear Juan, One correction here. Thales did also deliver an update of our individual exploitation plan following EC review. Thought it was communicated to you already but may be not. In any case it is now corrected. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena Envoy? : mardi 1 octobre 2013 15:59 ? : Heller, Markus Cc : fiware-wpl at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE Hi Markus Please find the list, regarding new confidential exploitation plans delivered after the review, below: o TID- Delivered o SAP- Delivered without any modification o IBM- No news o FT- No news o DT- No news o TI- Delivered o THALES- No news o ENG- No news o INTEL- Delivered o Atos- Delivered without any modification o SIEMENS- Delivered o NOKIA SIEMENS NETWORKS- No news o ALCATEL- Delivered o TECHNICOLOR- Delivered o NEC- Delivered Br Juan [cid:image001.png at 01CEBECC.11EA80F0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CEBECC.11EA80F0] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: Heller, Markus [mailto:markus.heller at sap.com] Sent: martes, 01 de octubre de 2013 15:48 To: Juan Bare?o Guerenabarrena Cc: fiware-wpl at lists.fi-ware.eu; jhierro at tid.es Subject: RE: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE Hi Juan, all, BTW do you or Juanjo have a statistics how many FI-WARE partners have indeed sent individual exploitation plans to EC after their first request immediately after the review? I am not sure if something about this is mentioned in the report who did or who did not, do you know? Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Montag, 30. September 2013 15:59 To: Juan Bare?o Guerenabarrena; jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Dear All We can summary the previous mail with the Recommendation 12, see below, so it is clear that they demand new confidential individual exploitation plans, but we have to confirm that this replaces the 11.2.2 resubmission, as they mentioned before in the Outcome document. Recommendation 12 (Page 12- FI WARE Review 5 Report) Provide a credible and precise exploitation plan for each partner who provides a GE implementation. Such information was orally requested by the European Commission Project Officer at the end of the Month 24 Review Meeting. The information must be submitted before the end of October 2013. It may be submitted by the partner concerned on a confidential basis to the European Commission Project Officer. It is expected that the exploitation plans will cover all GE implementations to a sufficient degree demonstrating business commitment. [cid:image001.png at 01CEBECC.11EA80F0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CEBECC.11EA80F0] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: lunes, 30 de septiembre de 2013 15:26 To: jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Hi Juanjo Please find here enclosed the main comments on the exploitation side by the reviewers. In the first document about the Outcome, I have doubts about what exactly we have to provide (see paragraph in red), exploitation plans by GE implementation of each owner?? In each individual exploitation plan define the exploitation plans by GE implementation??...notes that they said that the resubmission of D11.2.2 is replaced by this request for confidential plans, so resubmission for D11.2.2 is not necessary??.........but for sure we all have to work in a new and agreed version for next year review or we have to resubmit D11.2.2, right now, with the strategic vision we shared in the review properly included? I enclosed you also the feedback on the individual exploitation plans form the FI WARE Review Report, I will come back with additional comments regarding exploitation an Action Plan needed, but first it is important to Know what exactly we have to provide by 31 October 2013, regarding exploitation Thanks for your support Juan - 1_ Outcome FI WARE Review: (Page 3): Therefore, the Commission requests exploitation plans: o For all GE implementations except the 16 above-mentioned GE implementations with open source software licenses, so for the 32 and other GE implementations that are not (yet) in the Catalogue. The cockpit contains several of those. o To be provided by the GE implementation owner, irrespective of the type of organization, so commercial or not. Organizations that joined the consortium as a result of a competitive call for additional beneficiaries and their GE implementations are excluded. o To be sent directly to the Commission. o To be provided before 31 October 2013. In case no document is received by that date, the latest available version will be used, i.e. deliverable D11.2.2 or individual exploitation plans sent to the Commission after the last review meeting (the confidential ones). o To be provided instead of the requested resubmission of deliverable D11.2.2. The review report requests a resubmission of D11.2.2 for month 30 . This is replaced by this request for confidential, individual exploitation plans. The received or latest exploitation plans will be evaluated. Use of the respective GE implementations by the phase 2 use case projects will also be considered. The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project. - 2_ FI WARE Review 5 Report: o Pag 4. In line with the above requested: Exploitation of project results by FI-WARE partners ? The (lack of) substance and concreteness for the vast majority of the individual exploitation plans, at Month 24, is totally inappropriate for the ambition of FI-WARE and incommensurate with the claimed business commitment to project results by the main partners, even to Vice-President Kroes. As for the previous period, there is no visible attempt to echo - let alone apply - the well-elaborated business and ecosystem analysis to the individual partners' own approach and planning regarding project results. The reviewers are exceedingly concerned about the dearth of concrete evidence of the business commitment of GE implementation owners, and the corresponding lack of concrete information and traceability of GE implementations in the exploitation plans of these owners. - (Page 50)- Feedback regarding Individual Exploitation plans: D11.2.2 Exploitation Plan, including IPR Management o Unfortunately, despite the repeated comments by the reviewers on this very subject, the specific company exploitation plans are still generic and in some cases bordering on being a "wish list". They all say positive things but lack specificity in themes, markets, applications, timeline, budget and resources dedicated to the success of FI-WARE. With a few exceptions such as those supplied by ATOS and Thales and to some extent Telefonica and France Telecom, the individual exploitation plans are largely a collection of wishes, expectations and high level aims o In all cases, there are surprisingly very few references to specific GEs (or GE combinations) even by the owners concerned. In addition, they are a collation of single plans without any attempt to explain which type of synchronisation or coordination will happen among them and how this concerted effort will be coordinated, if any. There is not a single reference in the individual plans to the OIL, which is positioned in the generic part of the document as a key vehicle to "pave the way for a successful exploitation and sustainability of its [the FI-WARE project] results". [cid:image001.png at 01CEBECC.11EA80F0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CEBECC.11EA80F0] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: jueves, 26 de septiembre de 2013 15:33 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: FI-WARE - Outcome Letter & Review report Dear FI-WARE partners, Please find enclosed the report of the last review meeting. I haven't had time to review it in detail, just a very quick reading of the summary sections. Overall, I'm satisfied with the results and I tend to agree with some of the points about which the review establish we should implement remedies: * Improvement of the backlog management (this has led to rejection of the backlog deliverables and, most probably, the rejection of the Technical Roadmap deliverable). * Deep and carefully revision of contents in the FI-WARE Catalogue, overall regarding the all which has to do with terms and conditions of usage beyond the FI-PPP * Re-submission of Security Open Specifications. Apparently (at least considering those pieces I have read) this has to do with the IdM GE Open Specifications, so the good news is that we are already working to solve this issue. More kind of a surprise to me is the rejection of the following deliverables: * Deliverables linked the Tools chapter. * Report on validation by Use Case projects. * Exploitation Plan (given the fact that the consortium deliverable may be not satisfactory enough, but I was hoping that the individual exploitation plans shared in confidentiality with the EC had been more convincing ...) We will need to read the review more carefully to understand the reasons why those deliverables have been rejected. On the other hand, I'm happy to see that most of the chapter technical deliverables have been accepted. Unfortunately, the review could not incorporate results of the successful launch of FI-LAB at the Campus Party Europe event, because this took place after the review meeting. If so, I'm pretty sure that the analysis had been more favorable. This is a very raw analysis. Please don't consider it complete. We need more time to digest the whole report. Let's make a more close analysis and come back with a detailed action plan. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE - Outcome Letter & Review report Date: Thu, 26 Sep 2013 12:56:19 +0000 From: To: CC: , , , , , , , Dear Mr Hierro, Please find attached a copy of the outcome letter and review report of project 285248 FI-WARE. Please acknowledge receipt of this letter. Many thanks in advance Best regards, Vanessa Vanhumbeeck European Commission DG CONNECT Unit E3 - Net Innovation Tel.: +32 2 296 49 39 Email: vanessa.vanhumbeeck at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: From juan.bareno at atos.net Tue Oct 1 17:33:09 2013 From: juan.bareno at atos.net (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Tue, 1 Oct 2013 17:33:09 +0200 Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter &Reviewreport-EXPLOITATION SIDE Message-ID: Ok Thanks Pascal Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: martes, 01 de octubre de 2013 17:32 To: Juan Bare?o Guerenabarrena Cc: fiware-wpl at lists.fi-ware.eu; SIEUX Corinne Subject: Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter &Reviewreport-EXPLOITATION SIDE Dear Juan, One correction here. Thales did also deliver an update of our individual exploitation plan following EC review. Thought it was communicated to you already but may be not. In any case it is now corrected. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena Envoy? : mardi 1 octobre 2013 15:59 ? : Heller, Markus Cc : fiware-wpl at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE Hi Markus Please find the list, regarding new confidential exploitation plans delivered after the review, below: o TID- Delivered o SAP- Delivered without any modification o IBM- No news o FT- No news o DT- No news o TI- Delivered o THALES- No news o ENG- No news o INTEL- Delivered o Atos- Delivered without any modification o SIEMENS- Delivered o NOKIA SIEMENS NETWORKS- No news o ALCATEL- Delivered o TECHNICOLOR- Delivered o NEC- Delivered Br Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: Heller, Markus [mailto:markus.heller at sap.com] Sent: martes, 01 de octubre de 2013 15:48 To: Juan Bare?o Guerenabarrena Cc: fiware-wpl at lists.fi-ware.eu; jhierro at tid.es Subject: RE: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE Hi Juan, all, BTW do you or Juanjo have a statistics how many FI-WARE partners have indeed sent individual exploitation plans to EC after their first request immediately after the review? I am not sure if something about this is mentioned in the report who did or who did not, do you know? Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Montag, 30. September 2013 15:59 To: Juan Bare?o Guerenabarrena; jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Dear All We can summary the previous mail with the Recommendation 12, see below, so it is clear that they demand new confidential individual exploitation plans, but we have to confirm that this replaces the 11.2.2 resubmission, as they mentioned before in the Outcome document. Recommendation 12 (Page 12- FI WARE Review 5 Report) Provide a credible and precise exploitation plan for each partner who provides a GE implementation. Such information was orally requested by the European Commission Project Officer at the end of the Month 24 Review Meeting. The information must be submitted before the end of October 2013. It may be submitted by the partner concerned on a confidential basis to the European Commission Project Officer. It is expected that the exploitation plans will cover all GE implementations to a sufficient degree demonstrating business commitment. Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: lunes, 30 de septiembre de 2013 15:26 To: jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Hi Juanjo Please find here enclosed the main comments on the exploitation side by the reviewers. In the first document about the Outcome, I have doubts about what exactly we have to provide (see paragraph in red), exploitation plans by GE implementation of each owner?? In each individual exploitation plan define the exploitation plans by GE implementation??...notes that they said that the resubmission of D11.2.2 is replaced by this request for confidential plans, so resubmission for D11.2.2 is not necessary??.........but for sure we all have to work in a new and agreed version for next year review or we have to resubmit D11.2.2, right now, with the strategic vision we shared in the review properly included? I enclosed you also the feedback on the individual exploitation plans form the FI WARE Review Report, I will come back with additional comments regarding exploitation an Action Plan needed, but first it is important to Know what exactly we have to provide by 31 October 2013, regarding exploitation Thanks for your support Juan - 1_ Outcome FI WARE Review: (Page 3): Therefore, the Commission requests exploitation plans: o For all GE implementations except the 16 above-mentioned GE implementations with open source software licenses, so for the 32 and other GE implementations that are not (yet) in the Catalogue. The cockpit contains several of those. o To be provided by the GE implementation owner, irrespective of the type of organization, so commercial or not. Organizations that joined the consortium as a result of a competitive call for additional beneficiaries and their GE implementations are excluded. o To be sent directly to the Commission. o To be provided before 31 October 2013. In case no document is received by that date, the latest available version will be used, i.e. deliverable D11.2.2 or individual exploitation plans sent to the Commission after the last review meeting (the confidential ones). o To be provided instead of the requested resubmission of deliverable D11.2.2. The review report requests a resubmission of D11.2.2 for month 30 . This is replaced by this request for confidential, individual exploitation plans. The received or latest exploitation plans will be evaluated. Use of the respective GE implementations by the phase 2 use case projects will also be considered. The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project. - 2_ FI WARE Review 5 Report: o Pag 4. In line with the above requested: Exploitation of project results by FI-WARE partners ? The (lack of) substance and concreteness for the vast majority of the individual exploitation plans, at Month 24, is totally inappropriate for the ambition of FI-WARE and incommensurate with the claimed business commitment to project results by the main partners, even to Vice-President Kroes. As for the previous period, there is no visible attempt to echo - let alone apply - the well-elaborated business and ecosystem analysis to the individual partners' own approach and planning regarding project results. The reviewers are exceedingly concerned about the dearth of concrete evidence of the business commitment of GE implementation owners, and the corresponding lack of concrete information and traceability of GE implementations in the exploitation plans of these owners. - (Page 50)- Feedback regarding Individual Exploitation plans: D11.2.2 Exploitation Plan, including IPR Management o Unfortunately, despite the repeated comments by the reviewers on this very subject, the specific company exploitation plans are still generic and in some cases bordering on being a "wish list". They all say positive things but lack specificity in themes, markets, applications, timeline, budget and resources dedicated to the success of FI-WARE. With a few exceptions such as those supplied by ATOS and Thales and to some extent Telefonica and France Telecom, the individual exploitation plans are largely a collection of wishes, expectations and high level aims o In all cases, there are surprisingly very few references to specific GEs (or GE combinations) even by the owners concerned. In addition, they are a collation of single plans without any attempt to explain which type of synchronisation or coordination will happen among them and how this concerted effort will be coordinated, if any. There is not a single reference in the individual plans to the OIL, which is positioned in the generic part of the document as a key vehicle to "pave the way for a successful exploitation and sustainability of its [the FI-WARE project] results". Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: jueves, 26 de septiembre de 2013 15:33 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: FI-WARE - Outcome Letter & Review report Dear FI-WARE partners, Please find enclosed the report of the last review meeting. I haven't had time to review it in detail, just a very quick reading of the summary sections. Overall, I'm satisfied with the results and I tend to agree with some of the points about which the review establish we should implement remedies: * Improvement of the backlog management (this has led to rejection of the backlog deliverables and, most probably, the rejection of the Technical Roadmap deliverable). * Deep and carefully revision of contents in the FI-WARE Catalogue, overall regarding the all which has to do with terms and conditions of usage beyond the FI-PPP * Re-submission of Security Open Specifications. Apparently (at least considering those pieces I have read) this has to do with the IdM GE Open Specifications, so the good news is that we are already working to solve this issue. More kind of a surprise to me is the rejection of the following deliverables: * Deliverables linked the Tools chapter. * Report on validation by Use Case projects. * Exploitation Plan (given the fact that the consortium deliverable may be not satisfactory enough, but I was hoping that the individual exploitation plans shared in confidentiality with the EC had been more convincing ...) We will need to read the review more carefully to understand the reasons why those deliverables have been rejected. On the other hand, I'm happy to see that most of the chapter technical deliverables have been accepted. Unfortunately, the review could not incorporate results of the successful launch of FI-LAB at the Campus Party Europe event, because this took place after the review meeting. If so, I'm pretty sure that the analysis had been more favorable. This is a very raw analysis. Please don't consider it complete. We need more time to digest the whole report. Let's make a more close analysis and come back with a detailed action plan. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE - Outcome Letter & Review report Date: Thu, 26 Sep 2013 12:56:19 +0000 From: To: CC: , , , , , , , Dear Mr Hierro, Please find attached a copy of the outcome letter and review report of project 285248 FI-WARE. Please acknowledge receipt of this letter. Many thanks in advance Best regards, Vanessa Vanhumbeeck European Commission DG CONNECT Unit E3 - Net Innovation Tel.: +32 2 296 49 39 Email: vanessa.vanhumbeeck at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: From markus.heller at sap.com Tue Oct 1 17:41:54 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 1 Oct 2013 15:41:54 +0000 Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter &Reviewreport-EXPLOITATION SIDE In-Reply-To: References: Message-ID: <393554EDCF801348BC53C7813C6CB73B19CAB61B@DEWDFEMB14A.global.corp.sap> Hi Juan, thank you for your info and best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Dienstag, 1. Oktober 2013 17:33 To: BISSON Pascal Cc: fiware-wpl at lists.fi-ware.eu; SIEUX Corinne Subject: Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter &Reviewreport-EXPLOITATION SIDE Ok Thanks Pascal [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: martes, 01 de octubre de 2013 17:32 To: Juan Bare?o Guerenabarrena Cc: fiware-wpl at lists.fi-ware.eu; SIEUX Corinne Subject: Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter &Reviewreport-EXPLOITATION SIDE Dear Juan, One correction here. Thales did also deliver an update of our individual exploitation plan following EC review. Thought it was communicated to you already but may be not. In any case it is now corrected. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena Envoy? : mardi 1 octobre 2013 15:59 ? : Heller, Markus Cc : fiware-wpl at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE Hi Markus Please find the list, regarding new confidential exploitation plans delivered after the review, below: o TID- Delivered o SAP- Delivered without any modification o IBM- No news o FT- No news o DT- No news o TI- Delivered o THALES- No news o ENG- No news o INTEL- Delivered o Atos- Delivered without any modification o SIEMENS- Delivered o NOKIA SIEMENS NETWORKS- No news o ALCATEL- Delivered o TECHNICOLOR- Delivered o NEC- Delivered Br Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: Heller, Markus [mailto:markus.heller at sap.com] Sent: martes, 01 de octubre de 2013 15:48 To: Juan Bare?o Guerenabarrena Cc: fiware-wpl at lists.fi-ware.eu; jhierro at tid.es Subject: RE: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Reviewreport-EXPLOITATION SIDE Hi Juan, all, BTW do you or Juanjo have a statistics how many FI-WARE partners have indeed sent individual exploitation plans to EC after their first request immediately after the review? I am not sure if something about this is mentioned in the report who did or who did not, do you know? Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Montag, 30. September 2013 15:59 To: Juan Bare?o Guerenabarrena; jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Dear All We can summary the previous mail with the Recommendation 12, see below, so it is clear that they demand new confidential individual exploitation plans, but we have to confirm that this replaces the 11.2.2 resubmission, as they mentioned before in the Outcome document. Recommendation 12 (Page 12- FI WARE Review 5 Report) Provide a credible and precise exploitation plan for each partner who provides a GE implementation. Such information was orally requested by the European Commission Project Officer at the end of the Month 24 Review Meeting. The information must be submitted before the end of October 2013. It may be submitted by the partner concerned on a confidential basis to the European Commission Project Officer. It is expected that the exploitation plans will cover all GE implementations to a sufficient degree demonstrating business commitment. [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: lunes, 30 de septiembre de 2013 15:26 To: jhierro at tid.es Cc: fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] FW: Fwd: FI-WARE - Outcome Letter & Review report-EXPLOITATION SIDE Hi Juanjo Please find here enclosed the main comments on the exploitation side by the reviewers. In the first document about the Outcome, I have doubts about what exactly we have to provide (see paragraph in red), exploitation plans by GE implementation of each owner?? In each individual exploitation plan define the exploitation plans by GE implementation??...notes that they said that the resubmission of D11.2.2 is replaced by this request for confidential plans, so resubmission for D11.2.2 is not necessary??.........but for sure we all have to work in a new and agreed version for next year review or we have to resubmit D11.2.2, right now, with the strategic vision we shared in the review properly included? I enclosed you also the feedback on the individual exploitation plans form the FI WARE Review Report, I will come back with additional comments regarding exploitation an Action Plan needed, but first it is important to Know what exactly we have to provide by 31 October 2013, regarding exploitation Thanks for your support Juan - 1_ Outcome FI WARE Review: (Page 3): Therefore, the Commission requests exploitation plans: o For all GE implementations except the 16 above-mentioned GE implementations with open source software licenses, so for the 32 and other GE implementations that are not (yet) in the Catalogue. The cockpit contains several of those. o To be provided by the GE implementation owner, irrespective of the type of organization, so commercial or not. Organizations that joined the consortium as a result of a competitive call for additional beneficiaries and their GE implementations are excluded. o To be sent directly to the Commission. o To be provided before 31 October 2013. In case no document is received by that date, the latest available version will be used, i.e. deliverable D11.2.2 or individual exploitation plans sent to the Commission after the last review meeting (the confidential ones). o To be provided instead of the requested resubmission of deliverable D11.2.2. The review report requests a resubmission of D11.2.2 for month 30 . This is replaced by this request for confidential, individual exploitation plans. The received or latest exploitation plans will be evaluated. Use of the respective GE implementations by the phase 2 use case projects will also be considered. The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project. - 2_ FI WARE Review 5 Report: o Pag 4. In line with the above requested: Exploitation of project results by FI-WARE partners ? The (lack of) substance and concreteness for the vast majority of the individual exploitation plans, at Month 24, is totally inappropriate for the ambition of FI-WARE and incommensurate with the claimed business commitment to project results by the main partners, even to Vice-President Kroes. As for the previous period, there is no visible attempt to echo - let alone apply - the well-elaborated business and ecosystem analysis to the individual partners' own approach and planning regarding project results. The reviewers are exceedingly concerned about the dearth of concrete evidence of the business commitment of GE implementation owners, and the corresponding lack of concrete information and traceability of GE implementations in the exploitation plans of these owners. - (Page 50)- Feedback regarding Individual Exploitation plans: D11.2.2 Exploitation Plan, including IPR Management o Unfortunately, despite the repeated comments by the reviewers on this very subject, the specific company exploitation plans are still generic and in some cases bordering on being a "wish list". They all say positive things but lack specificity in themes, markets, applications, timeline, budget and resources dedicated to the success of FI-WARE. With a few exceptions such as those supplied by ATOS and Thales and to some extent Telefonica and France Telecom, the individual exploitation plans are largely a collection of wishes, expectations and high level aims o In all cases, there are surprisingly very few references to specific GEs (or GE combinations) even by the owners concerned. In addition, they are a collation of single plans without any attempt to explain which type of synchronisation or coordination will happen among them and how this concerted effort will be coordinated, if any. There is not a single reference in the individual plans to the OIL, which is positioned in the generic part of the document as a key vehicle to "pave the way for a successful exploitation and sustainability of its [the FI-WARE project] results". [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: jueves, 26 de septiembre de 2013 15:33 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: FI-WARE - Outcome Letter & Review report Dear FI-WARE partners, Please find enclosed the report of the last review meeting. I haven't had time to review it in detail, just a very quick reading of the summary sections. Overall, I'm satisfied with the results and I tend to agree with some of the points about which the review establish we should implement remedies: * Improvement of the backlog management (this has led to rejection of the backlog deliverables and, most probably, the rejection of the Technical Roadmap deliverable). * Deep and carefully revision of contents in the FI-WARE Catalogue, overall regarding the all which has to do with terms and conditions of usage beyond the FI-PPP * Re-submission of Security Open Specifications. Apparently (at least considering those pieces I have read) this has to do with the IdM GE Open Specifications, so the good news is that we are already working to solve this issue. More kind of a surprise to me is the rejection of the following deliverables: * Deliverables linked the Tools chapter. * Report on validation by Use Case projects. * Exploitation Plan (given the fact that the consortium deliverable may be not satisfactory enough, but I was hoping that the individual exploitation plans shared in confidentiality with the EC had been more convincing ...) We will need to read the review more carefully to understand the reasons why those deliverables have been rejected. On the other hand, I'm happy to see that most of the chapter technical deliverables have been accepted. Unfortunately, the review could not incorporate results of the successful launch of FI-LAB at the Campus Party Europe event, because this took place after the review meeting. If so, I'm pretty sure that the analysis had been more favorable. This is a very raw analysis. Please don't consider it complete. We need more time to digest the whole report. Let's make a more close analysis and come back with a detailed action plan. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE - Outcome Letter & Review report Date: Thu, 26 Sep 2013 12:56:19 +0000 From: To: CC: , , , , , , , Dear Mr Hierro, Please find attached a copy of the outcome letter and review report of project 285248 FI-WARE. Please acknowledge receipt of this letter. Many thanks in advance Best regards, Vanessa Vanhumbeeck European Commission DG CONNECT Unit E3 - Net Innovation Tel.: +32 2 296 49 39 Email: vanessa.vanhumbeeck at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: From jhierro at tid.es Fri Oct 4 01:14:30 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 04 Oct 2013 01:14:30 +0200 Subject: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D076D0CC1@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D076D0CC1@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <524DFA56.4030308@tid.es> Hi all, Please find enclosed the technical report produced by Lutz Schubert regarding FI-WARE GEs. I haven't had time to review it carefully although in a very quick review I found several statements that suprised me and, mostly, it seems like a lot of the testing was made over versions of GEs which where not the ones delivered in release 2.2 or 2.3. Nevertheless, I pass the report to you. I have prepared a copy of the report at the following Google document: https://docs.google.com/document/d/1FVDmcUqamhfMhCDundzcrGwrLBYWF8xePUyic5Axr6A/edit I would kindly ask you to review the report and, in cooperation with GEi owners in your chapter, add a response (please add text in Blue after commented paragraphs) to the report. This way, we can quickly get a response to this report. Afterwards, we can discuss whether it is suitable to send such response back to the EC. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE: report by Lutz Schubert Date: Wed, 2 Oct 2013 15:37:43 +0000 From: To: , , CC: , Dear Juanjo, As indicated before, the assessment of prototypes during FI-WARE reviews is mostly based on the demos. I would like to have a better assessment of the prototypes, independent from the normal FI-WARE reviews. Therefore, Lutz Schubert from the University of Ulm (formerly with HLRS Stuttgart) has carried out this task. His report is attached. The report is the status as of 10 days ago, and might not be fully complete/consistent related to the Catalogue, the specifications of the wiki, etc. However, it does not make a lot of sense to try to perfect the assessment right now, as the report is clear of its main conclusions. A similar, second exercise could be done in (say) 6 months from now. Best regards, Arian ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FiWare_PPP_Evaluation v02.pdf Type: application/pdf Size: 985876 bytes Desc: not available URL: From jhierro at tid.es Fri Oct 4 01:19:55 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 04 Oct 2013 01:19:55 +0200 Subject: [Fiware-wpl] Fwd: FI-WARE: date month 30 review In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D076D0B49@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D076D0B49@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <524DFB9B.7060707@tid.es> Dear all, Please find the answer sent to me by Arian in response to my question about a next review. As you see, the EC asks for a 1-day review on non-technical matters during the week of December 2. I reluctant to agree on the proposed week ... I would rather prefer the week of December 16th ... but, of course, this is a topic to discuss during our next WPL/WPA follow-up confcall. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE: date month 30 review Date: Wed, 2 Oct 2013 13:20:45 +0000 From: To: , , CC: , , Dear Juanjo, The next review will be mostly about the new activities, the plans for life after FI-WARE, and not so much about the technical chapters. It will be a 1-day meeting, in Brussels. The best dates appear to be in the week of December 2, except Wed Dec 4. Would it be possible to fix a date in that period? Please let me know soon. Please keep Ragnar and Vanessa in copy, as I will not be in the next few weeks. Best regards, Arian ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri Oct 4 08:38:05 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 4 Oct 2013 06:38:05 +0000 Subject: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert In-Reply-To: <524DFA56.4030308@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D076D0CC1@S-DC-ESTF03-B.net1.cec.eu.int> <524DFA56.4030308@tid.es> Message-ID: <29611_1380868686_524E624E_29611_13039_1_976A65C5A08ADF49B9A8523F7F81925C114E45@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi All, I am also a bit surprised by this review especially because in many cases, it refers to release 2.2 software packages and not to release 2.3 (it is typically the case for IoT but also for many other chapter after a very quick reading). But I'm sure that Miguel can confirm what are the documentation and packages we sent to Mr Lutz Schubert (I have some emails at the beginning of August) Recommendation 1: easy installation package... We did some progress especially in the SaaS approach with recipes but it was clearly not the approach following during this evaluation (stand alone evaluation) Recommendation 2: I've raised this issue previously that we missed at least the architecture picture to understand why different chapters and how some GE can interact with some other. For the comment regarding inclusion of specific use cases per GE to illustrate how to use them, we can bridge this point with the missing white paper, but again we will change the content of the white paper, and it is not aligned on what we can find in any Open Source community website: use case scenario per component. We can envisage easily on the first page an introduction for each chapter and the the list of GE per chapter and their role in the architecture Recommendation 3: Clearly the catalogue was not the 1st priority in July and the content was not aligned with the R2.3 delivery BUT we do not have to explain compatibility between the different license models! If you want to know the compatibility between a GPL and a L-GPL today, you have to do this work yourself based on the documentation you have for the different licenses. What is clearly missing for some GEs is the license model and details. So the weak feedback is for me globally related to the delays we had with release R2.3 (and I'm not pointing anybody for that, we are on the same boat) trying to improve everything for the Campus Party. And I'm sure that Future Networks and Ogilvy have some comments on our catalogue. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 4 octobre 2013 01:15 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert Hi all, Please find enclosed the technical report produced by Lutz Schubert regarding FI-WARE GEs. I haven't had time to review it carefully although in a very quick review I found several statements that suprised me and, mostly, it seems like a lot of the testing was made over versions of GEs which where not the ones delivered in release 2.2 or 2.3. Nevertheless, I pass the report to you. I have prepared a copy of the report at the following Google document: https://docs.google.com/document/d/1FVDmcUqamhfMhCDundzcrGwrLBYWF8xePUyic5Axr6A/edit I would kindly ask you to review the report and, in cooperation with GEi owners in your chapter, add a response (please add text in Blue after commented paragraphs) to the report. This way, we can quickly get a response to this report. Afterwards, we can discuss whether it is suitable to send such response back to the EC. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE: report by Lutz Schubert Date: Wed, 2 Oct 2013 15:37:43 +0000 From: To: , , CC: , Dear Juanjo, As indicated before, the assessment of prototypes during FI-WARE reviews is mostly based on the demos. I would like to have a better assessment of the prototypes, independent from the normal FI-WARE reviews. Therefore, Lutz Schubert from the University of Ulm (formerly with HLRS Stuttgart) has carried out this task. His report is attached. The report is the status as of 10 days ago, and might not be fully complete/consistent related to the Catalogue, the specifications of the wiki, etc. However, it does not make a lot of sense to try to perfect the assessment right now, as the report is clear of its main conclusions. A similar, second exercise could be done in (say) 6 months from now. Best regards, Arian ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From depa at eng.it Fri Oct 4 09:29:30 2013 From: depa at eng.it (depa at eng.it) Date: Fri, 4 Oct 2013 07:29:30 +0000 Subject: [Fiware-wpl] R: Re: Fwd: FI-WARE: report by Lutz Schubert In-Reply-To: <29611_1380868686_524E624E_29611_13039_1_976A65C5A08ADF49B9A8523F7F81925C114E45@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <69AD1A9684E7184DADBE43806285BA9D076D0CC1@S-DC-ESTF03-B.net1.cec.eu.int> <524DFA56.4030308@tid.es> <29611_1380868686_524E624E_29611_13039_1_976A65C5A08ADF49B9A8523F7F81925C114E45@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2051839771-1380871794-cardhu_decombobulator_blackberry.rim.net-232766958-@b25.c14.bise7.blackberry> Dear thierry and all, I'm surprised you are surprised: clearly lutz made his evaluation on what easier available to him and this was 2.2. If we all believe 2.3 fixes most of his comments, this is wonderful, otherwise we can his comments on board as most convenient and beneficial to us. I tend to agree with the answer very positively provided by thierry! In addition more requirements are requested for our catalogue: yesterday from the 1.8 infoday jesus asked to have explicitely mention which standards each ge is compliant with although i replied they are well mentioned and described in the relevant spec. Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: thierry.nagellen at orange.com Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Fri, 04 Oct 2013 06:38:05 To: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From thierry.nagellen at orange.com Fri Oct 4 10:10:16 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 4 Oct 2013 08:10:16 +0000 Subject: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert In-Reply-To: <2051839771-1380871794-cardhu_decombobulator_blackberry.rim.net-232766958-@b25.c14.bise7.blackberry> References: <69AD1A9684E7184DADBE43806285BA9D076D0CC1@S-DC-ESTF03-B.net1.cec.eu.int> <524DFA56.4030308@tid.es> <29611_1380868686_524E624E_29611_13039_1_976A65C5A08ADF49B9A8523F7F81925C114E45@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2051839771-1380871794-cardhu_decombobulator_blackberry.rim.net-232766958-@b25.c14.bise7.blackberry> Message-ID: <16137_1380874216_524E77E8_16137_6808_1_976A65C5A08ADF49B9A8523F7F81925C114EC1@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear Stefano My point was that the software packages were, in general (again very quick reading of Fi-Ware and Fi-Ware restricted files repository), available for R2.3 mid or end of July. I would clearly know what was the process for Mr Schubert: 1- Going only through the catalogue and use the links on catalogue pages (in this case the catalogue update could be the concern) 2- Using documentation provided by Miguel and additional direct links to find the right software packages in Fi-Ware & Fi-Ware-PPP-Restricted files repository If the evaluation was only through what was available through the catalogue, catalogue update is always a major issue, and as explained during the last WPL meeting we have another inconsistency now with links to the public wiki which are not aligned with the downloadable version (and stable). Catalogue shows release 2.3 when wiki pages are now describing R3.1 version. Adding the standards in the catalogue will also add complexity: where is the best place for that because we should also simplify the number of window tabs we have. BR Thierry -----Message d'origine----- De?: depa at eng.it [mailto:depa at eng.it] Envoy??: vendredi 4 octobre 2013 09:30 ??: NAGELLEN Thierry IMT/OLPS; Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: R: Re: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert Dear thierry and all, I'm surprised you are surprised: clearly lutz made his evaluation on what easier available to him and this was 2.2. If we all believe 2.3 fixes most of his comments, this is wonderful, otherwise we can his comments on board as most convenient and beneficial to us. I tend to agree with the answer very positively provided by thierry! In addition more requirements are requested for our catalogue: yesterday from the 1.8 infoday jesus asked to have explicitely mention which standards each ge is compliant with although i replied they are well mentioned and described in the relevant spec. Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: thierry.nagellen at orange.com Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Fri, 04 Oct 2013 06:38:05 To: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. From stefano.depanfilis at eng.it Fri Oct 4 10:36:52 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Fri, 4 Oct 2013 10:36:52 +0200 Subject: [Fiware-wpl] Fwd: FI-WARE: date month 30 review In-Reply-To: <524DFB9B.7060707@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D076D0B49@S-DC-ESTF03-B.net1.cec.eu.int> <524DFB9B.7060707@tid.es> Message-ID: dear juanjo, i think arian is proposing that week becouse on 4th dec he will have also the xifi review, so just optimisation from his side. i do not mind to have the review in the same suggested week. ciao, stefano 2013/10/4 Juanjo Hierro > Dear all, > > Please find the answer sent to me by Arian in response to my question > about a next review. > > As you see, the EC asks for a 1-day review on non-technical matters > during the week of December 2. > > I reluctant to agree on the proposed week ... I would rather prefer the > week of December 16th ... but, of course, this is a topic to discuss during > our next WPL/WPA follow-up confcall. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > FI-PPP Architecture Board chairman > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > > -------- Original Message -------- Subject: FI-WARE: date month 30 review Date: > Wed, 2 Oct 2013 13:20:45 +0000 From: To: > , , > CC: , > , > > > Dear Juanjo, > > > > The next review will be mostly about the new activities, the plans for > life after FI-WARE, and not so much about the technical chapters. > > > > It will be a 1-day meeting, in Brussels. > > > > The best dates appear to be in the week of December 2, except Wed Dec 4. > > > > Would it be possible to fix a date in that period? > > Please let me know soon. > > Please keep Ragnar and Vanessa in copy, as I will not be in the next few > weeks. > > > > Best regards, > > Arian > > > > > > ------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Fri Oct 4 10:46:38 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Fri, 4 Oct 2013 10:46:38 +0200 Subject: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert In-Reply-To: <16137_1380874216_524E77E8_16137_6808_1_976A65C5A08ADF49B9A8523F7F81925C114EC1@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <69AD1A9684E7184DADBE43806285BA9D076D0CC1@S-DC-ESTF03-B.net1.cec.eu.int> <524DFA56.4030308@tid.es> <29611_1380868686_524E624E_29611_13039_1_976A65C5A08ADF49B9A8523F7F81925C114E45@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2051839771-1380871794-cardhu_decombobulator_blackberry.rim.net-232766958-@b25.c14.bise7.blackberry> <16137_1380874216_524E77E8_16137_6808_1_976A65C5A08ADF49B9A8523F7F81925C114EC1@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: dear thierry, you perfectly rise the problem: the cataloues is our main window (!!!!) and it cannot be left as a second priority. everybody in the world see it and only after being attracted goes to the wiki, this is normal i'm afraid ..... for the standards i suggest a new header either in the "overview" or in the "documentation" page of each ge with a line text, no more. ciao, stefano 2013/10/4 : > Dear Stefano > > My point was that the software packages were, in general (again very quick reading of Fi-Ware and Fi-Ware restricted files repository), available for R2.3 mid or end of July. I would clearly know what was the process for Mr Schubert: > 1- Going only through the catalogue and use the links on catalogue pages (in this case the catalogue update could be the concern) > 2- Using documentation provided by Miguel and additional direct links to find the right software packages in Fi-Ware & Fi-Ware-PPP-Restricted files repository > > If the evaluation was only through what was available through the catalogue, catalogue update is always a major issue, and as explained during the last WPL meeting we have another inconsistency now with links to the public wiki which are not aligned with the downloadable version (and stable). > Catalogue shows release 2.3 when wiki pages are now describing R3.1 version. > > Adding the standards in the catalogue will also add complexity: where is the best place for that because we should also simplify the number of window tabs we have. > > BR > Thierry > > -----Message d'origine----- > De : depa at eng.it [mailto:depa at eng.it] > Envoy? : vendredi 4 octobre 2013 09:30 > ? : NAGELLEN Thierry IMT/OLPS; Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : R: Re: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert > > Dear thierry and all, > > I'm surprised you are surprised: clearly lutz made his evaluation on what easier available to him and this was 2.2. > > If we all believe 2.3 fixes most of his comments, this is wonderful, otherwise we can his comments on board as most convenient and beneficial to us. > > I tend to agree with the answer very positively provided by thierry! > In addition more requirements are requested for our catalogue: yesterday from the 1.8 infoday jesus asked to have explicitely mention which standards each ge is compliant with although i replied they are well mentioned and described in the relevant spec. > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: thierry.nagellen at orange.com > Sender: fiware-wpl-bounces at lists.fi-ware.eu > Date: Fri, 04 Oct 2013 06:38:05 > To: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 From mev at tid.es Fri Oct 4 10:50:10 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 04 Oct 2013 08:50:10 +0000 Subject: [Fiware-wpl] Agile dynamic - closing sprint planning - day 7 at 18:00 CET Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890B47BE@EX10-MB2-MAD.hi.inet> Dear Partners, Let me inform you that we are closing the sprint planning time slot on day 7 at 18:00 CET. Please, have it ready before that time because I'll get them a snapshot of the trackers and wiki to review the content with your corresponding WP Leaders. Thanks for cooperation!! If anything, please, let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Fri Oct 4 17:22:51 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 4 Oct 2013 15:22:51 +0000 Subject: [Fiware-wpl] [Fiware-ge-owners] Agile dynamic - closing sprint planning - day 7 at 18:00 CET In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B890B47BE@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890B47BE@EX10-MB2-MAD.hi.inet> Message-ID: <393554EDCF801348BC53C7813C6CB73B19CAD7CB@DEWDFEMB14A.global.corp.sap> Dear Manuel, I have left out the "GE-owners" mailing list here because I think it is sufficient to share in the small round my questions below since I more or less ask you for a short info session in the WPL/WPA meeting next week.. Meant as a rather small request for information. We had sent the "Backlog" deliverable multiple times to EC until now. But this time you are intending to change the format of the deliverable report, if I have understood right, which raises two questions: 1. Deliverable format (changes): What is the format / which level of detail to be used this time? Does something change ? Do you have an example of the deliverable format? 2. Time plan: What is the full time plan until delivery to EC? IMHO it would be good to first review/approve the delivery format and then have a final deadline to provide missing input. "Day 7" would be too short for a final delivery to EC, I guess? Is the deadline _end_ of October? For example, could I ask you if you can please conduct an information/review round in the WPL/WPA meeting next Monday, that from my side would solve my questions and we can proceed with the unchanged speed for delivery. Of course, if such (format) information has been shared before, please just let me know... Best wishes & nice weekend to all, Markus From: fiware-ge-owners-bounces at lists.fi-ware.eu [mailto:fiware-ge-owners-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Freitag, 4. Oktober 2013 10:50 To: fiware-ge-owners at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-ge-owners] Agile dynamic - closing sprint planning - day 7 at 18:00 CET Dear Partners, Let me inform you that we are closing the sprint planning time slot on day 7 at 18:00 CET. Please, have it ready before that time because I'll get them a snapshot of the trackers and wiki to review the content with your corresponding WP Leaders. Thanks for cooperation!! If anything, please, let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Fri Oct 4 17:35:07 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 4 Oct 2013 15:35:07 +0000 Subject: [Fiware-wpl] Validation deliverable and content Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6648604B32B@DEWDFEMB11A.global.corp.sap> Dear colleagues, please find attached the validation deliverable overview which I already anticipated to have ready for the Monday morning session. I anticipated some possible findings out of the bare-numbers and provided answers in the pptx-format as it allows deeper discussion and later we can more easily render this to the written deliverable (hopefully with less peer-review rounds). Any feedback, improvements, other findings or suggestions on how to enhance the approach, highly appreciated. For Monday I would propose to discuss - on the format and further content we want to submit - agree on the delivery timeline (end of October, as requested by the last review report) - discuss further findings and comment the findings I proposed As well I attached the current validation XLS for your deeper analysis and further information. You can find more background and the scenario based answers on the following link: https://forge.fi-ware.eu/docman/admin/index.php?group_id=27&selected_doc_group_id=420&language_id=&selected_stateid=5 (the validation Folder in the private docman). Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2013-10-07-FI-WARE_validation_analysis.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 928342 bytes Desc: 2013-10-07-FI-WARE_validation_analysis.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2013-10-07-validation-answers-to-validation-questionnaire-phase-one_updated_september.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 179651 bytes Desc: 2013-10-07-validation-answers-to-validation-questionnaire-phase-one_updated_september.xlsx URL: From mev at tid.es Sat Oct 5 09:36:03 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Sat, 05 Oct 2013 07:36:03 +0000 Subject: [Fiware-wpl] [Fiware-ge-owners] Agile dynamic - closing sprint planning - day 7 at 18:00 CET In-Reply-To: <393554EDCF801348BC53C7813C6CB73B19CAD7CB@DEWDFEMB14A.global.corp.sap> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890B47BE@EX10-MB2-MAD.hi.inet> <393554EDCF801348BC53C7813C6CB73B19CAD7CB@DEWDFEMB14A.global.corp.sap> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890B49F5@EX10-MB2-MAD.hi.inet> Dear Markus, Thanks for sharing your concerns! I agree on holding the discussion at this level. Yes, the reason for changing are two mainly: a) the previous deliverables have been rejected b) the review report complains about its lack of structure (it was structured at chapter level) 1. The main idea is to get down the structure from chapter level to GEI level and to use the views and content provided by the dashboard reports; having graphs and items ordered according to roadmap, backlog, and historic provides an easy way to understand the evolution and content. Having improved hierarchies, gives a better understanding on what has been developed on the GEi. I also think it gives the GE owners an important motivation to keep the content on good shape. 2. Deadline for this deliverable is end of October. I understand your comments, however, I don't want us to loose context: exhaustive reports covering all aspects of the proposal approved in April by the management board are reported for the last 4 months, some chapters haven't provided support or contributions as the monitoring diagrams [1] show. In my opinion, we need to work with the already established work plan and time line. On Monday I won't be able to have a proposal ready, but I'll share it as soon as possible. Meanwhile, my request is to take much greater interest in 1) fixing all remaining issues and 2) getting the Agile dynamic as soon as possible. We need to demonstrate we are working properly. So my proposal is to keep working hard all this month long to get to the best shape by the end of the month. In general I think the delivery dynamic should be to meet as many deadlines as possible. I quite dislike just thinking of the delivery just the month before, which it's my general interpretation of the current dynamic. In this regard, Miguel and I are about to start a constant delivery awareness action so that we all bear deadlines and next due deliverables in mind. Have you all also a nice weekend!! Manuel [1] - https://forge.fi-ware.eu/docman/view.php/27/2857/Backlog-Improvement-monitoring.xlsx From: Heller, Markus [mailto:markus.heller at sap.com] Sent: viernes, 04 de octubre de 2013 17:23 To: MANUEL ESCRICHE VICENTE Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-ge-owners] Agile dynamic - closing sprint planning - day 7 at 18:00 CET Dear Manuel, I have left out the "GE-owners" mailing list here because I think it is sufficient to share in the small round my questions below since I more or less ask you for a short info session in the WPL/WPA meeting next week.. Meant as a rather small request for information. We had sent the "Backlog" deliverable multiple times to EC until now. But this time you are intending to change the format of the deliverable report, if I have understood right, which raises two questions: 1. Deliverable format (changes): What is the format / which level of detail to be used this time? Does something change ? Do you have an example of the deliverable format? 2. Time plan: What is the full time plan until delivery to EC? IMHO it would be good to first review/approve the delivery format and then have a final deadline to provide missing input. "Day 7" would be too short for a final delivery to EC, I guess? Is the deadline _end_ of October? For example, could I ask you if you can please conduct an information/review round in the WPL/WPA meeting next Monday, that from my side would solve my questions and we can proceed with the unchanged speed for delivery. Of course, if such (format) information has been shared before, please just let me know... Best wishes & nice weekend to all, Markus From: fiware-ge-owners-bounces at lists.fi-ware.eu [mailto:fiware-ge-owners-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Freitag, 4. Oktober 2013 10:50 To: fiware-ge-owners at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-ge-owners] Agile dynamic - closing sprint planning - day 7 at 18:00 CET Dear Partners, Let me inform you that we are closing the sprint planning time slot on day 7 at 18:00 CET. Please, have it ready before that time because I'll get them a snapshot of the trackers and wiki to review the content with your corresponding WP Leaders. Thanks for cooperation!! If anything, please, let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Sun Oct 6 23:02:40 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 06 Oct 2013 23:02:40 +0200 Subject: [Fiware-wpl] Fwd: Re: FI-WARE: date month 30 review In-Reply-To: <5251CF56.5000809@tid.es> References: <5251CF56.5000809@tid.es> Message-ID: <5251CFF0.3040909@tid.es> Don't know whether Arian will react or he's already on holidays ... but I have sent this email to him as well as Ragnar (I understand he will act as replacement) Did some of you have a chance to chat with Arian during the Infodays as to confirm when he will leave for holidays and for how long ? Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Re: FI-WARE: date month 30 review Date: Sun, 06 Oct 2013 23:00:06 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: subsidies at tid.es, mcp at tid.es, CNECT-ICT-285248 at ec.europa.eu, Ragnar.Bergstrom at ec.europa.eu, Maria-Concepcion.ANTON-GARCIA at ec.europa.eu, "Vanessa.VANHUMBEECK at ec.europa.eu" , "jhierro >> \"Juan J. Hierro\"" Dear Arian, After consultation with the rest of major partners, the proposed week of December 2 would not be suitable. Indeed, no date before December 16, for obvious reasons. Besides, Telefonica has already consumed the planned budget for travels for the year and no travels other than those already confirmed and planned a month ago will be approved. This without saying that most probably I will be on holidays from the week of December 16th. Telefonica would kindly propose having this review after Christmas holidays, maybe some day of the week starting on January 13 or 20. We guess having it end of December or beginning of January shouldn't make a big difference. I hope you will understand, apologies for any inconvenience, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 02/10/13 15:20, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The next review will be mostly about the new activities, the plans for life after FI-WARE, and not so much about the technical chapters. It will be a 1-day meeting, in Brussels. The best dates appear to be in the week of December 2, except Wed Dec 4. Would it be possible to fix a date in that period? Please let me know soon. Please keep Ragnar and Vanessa in copy, as I will not be in the next few weeks. Best regards, Arian ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From depa at eng.it Mon Oct 7 07:03:35 2013 From: depa at eng.it (depa at eng.it) Date: Mon, 7 Oct 2013 05:03:35 +0000 Subject: [Fiware-wpl] R: Fwd: Re: FI-WARE: date month 30 review In-Reply-To: <5251CFF0.3040909@tid.es> References: <5251CF56.5000809@tid.es> <5251CFF0.3040909@tid.es> Message-ID: <436171177-1381122235-cardhu_decombobulator_blackberry.rim.net-716606611-@b25.c14.bise7.blackberry> Dear Juanjo, No chance to really talk with him, but did not know there was the need to talk about this as no advice form you on the matter ...... Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Sun, 06 Oct 2013 23:02:40 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: Re: FI-WARE: date month 30 review _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From mcp at tid.es Mon Oct 7 10:35:03 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 07 Oct 2013 10:35:03 +0200 Subject: [Fiware-wpl] Minutes of meeting for today Message-ID: <52527237.90808@tid.es> Hi all, The link for today is https://docs.google.com/document/d/177vXY1OtTK2XtG5UlksdDru1SjROSqrr9tkhHLOOxgw/edit?pli=1# See you in a few minutes. Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From mcp at tid.es Mon Oct 7 16:05:04 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 07 Oct 2013 16:05:04 +0200 Subject: [Fiware-wpl] Installation and user programming guides reviewed In-Reply-To: <6A671820E63F0E4FB42453BD2D8A1B88046BA04A@itrmx010.italy.itroot.adnet> References: <6A671820E63F0E4FB42453BD2D8A1B88046BA04A@itrmx010.italy.itroot.adnet> Message-ID: <5252BF90.8080500@tid.es> Hi Mauro, Thanks for all the work. As discussed in private, from now on will will funnel all this info through the WPLs/WPAs, similarly as we have done in the past with my reviews. For everyone, a clarificaton: there are two review tracks that are decoupled, the one by engineering (in principle, more technical) and mine (in principle, more formal). Both need to be properly incorporated to the GE documentation. @GE owners: please avoid answering individually, the replies should be grouped per chapter by the WPLs @WPL/WPAs: please organize internally The original excel file goes attached. Best regards, Miguel El 03/10/2013 17:31, Pecetti Mauro escribi?: Dear all, we reviewed the Ge's guides (installation and administration guide and user and programming guide) about FI-WARE Project R2 Deliverables . In the attached document you can find our annotations. Don't hesitate to contact us for any questions. BR Mauro Pecetti mauro.pecetti at eng.it Engineering Ingegneria Informatica spa Via Riccardo Morandi, 32 - 00148 Roma Mob. +39-348.1334223 www.eng.it <> -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP-Release2.3.xls Type: application/vnd.ms-excel Size: 183808 bytes Desc: not available URL: From mcp at tid.es Mon Oct 7 18:40:45 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 07 Oct 2013 18:40:45 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Fwd: FI-WARE: report by Lutz Schubert In-Reply-To: <29611_1380868686_524E624E_29611_13039_1_976A65C5A08ADF49B9A8523F7F81925C114E45@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <69AD1A9684E7184DADBE43806285BA9D076D0CC1@S-DC-ESTF03-B.net1.cec.eu.int> <524DFA56.4030308@tid.es> <29611_1380868686_524E624E_29611_13039_1_976A65C5A08ADF49B9A8523F7F81925C114E45@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <5252E40D.5010003@tid.es> Dear all, Sorry for the late response, there is a loooong queue of pending issues in my inbox. 1) I enclose a couple of messages. I sent a few before but these are the last two ones. I gave him a first introductory talk (about 1 hour) to show him where the resources were and he never contacted me again. As you see in the enclosed emails, I basically sent him the info I collected from you and offered direct support from the relevant contacts. I am surprised that he has never contacted me again (or any of you as far as I am aware). 2) I initially said to him that R2.2 was safer at that stage (beginning of the summer- there was little of R2.3 at that point) but at the end of his work, of course he could have looked into R2.3 (or asked!) 3) If we make an excel list of GEs with the columns "name of GE/GEi on wiki", "name on catalogue" (just public ones, of course) and "name of binaries on Files" we would see that it is not that easy or obvious. The level of clarity depends on the chapter. I can tell you 'cause every time I tried to do mappings, it was sometimes a nightmare. So he's right here, at least in my personal opinion. And yes, one extra column would be the recipes not to mention the still not very numerous eLearning courses. A proper answer would be aligning everything, making sure that it is 100% consistent and delivering an excel file with everything in full order. But given the previous experience with R2.3 (still pending reviews, some after 3 iterations) I am sceptical that we could get something close to that in a short time unless we neglect R3. 4) Regardless of the cloud facilities and the recipes, the binary packages should install beautifully and he claims that it is not the case. We should do installation testing to check (do we have the resources? I doubt it) but I suspect that in some cases he's right. Best regards, Miguel El 04/10/2013 8:38, thierry.nagellen at orange.com escribi?: Hi All, I am also a bit surprised by this review especially because in many cases, it refers to release 2.2 software packages and not to release 2.3 (it is typically the case for IoT but also for many other chapter after a very quick reading). But I'm sure that Miguel can confirm what are the documentation and packages we sent to Mr Lutz Schubert (I have some emails at the beginning of August) Recommendation 1: easy installation package... We did some progress especially in the SaaS approach with recipes but it was clearly not the approach following during this evaluation (stand alone evaluation) Recommendation 2: I've raised this issue previously that we missed at least the architecture picture to understand why different chapters and how some GE can interact with some other. For the comment regarding inclusion of specific use cases per GE to illustrate how to use them, we can bridge this point with the missing white paper, but again we will change the content of the white paper, and it is not aligned on what we can find in any Open Source community website: use case scenario per component. We can envisage easily on the first page an introduction for each chapter and the the list of GE per chapter and their role in the architecture Recommendation 3: Clearly the catalogue was not the 1st priority in July and the content was not aligned with the R2.3 delivery BUT we do not have to explain compatibility between the different license models! If you want to know the compatibility between a GPL and a L-GPL today, you have to do this work yourself based on the documentation you have for the different licenses. What is clearly missing for some GEs is the license model and details. So the weak feedback is for me globally related to the delays we had with release R2.3 (and I'm not pointing anybody for that, we are on the same boat) trying to improve everything for the Campus Party. And I'm sure that Future Networks and Ogilvy have some comments on our catalogue. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 4 octobre 2013 01:15 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: FI-WARE: report by Lutz Schubert Hi all, Please find enclosed the technical report produced by Lutz Schubert regarding FI-WARE GEs. I haven't had time to review it carefully although in a very quick review I found several statements that suprised me and, mostly, it seems like a lot of the testing was made over versions of GEs which where not the ones delivered in release 2.2 or 2.3. Nevertheless, I pass the report to you. I have prepared a copy of the report at the following Google document: https://docs.google.com/document/d/1FVDmcUqamhfMhCDundzcrGwrLBYWF8xePUyic5Axr6A/edit I would kindly ask you to review the report and, in cooperation with GEi owners in your chapter, add a response (please add text in Blue after commented paragraphs) to the report. This way, we can quickly get a response to this report. Afterwards, we can discuss whether it is suitable to send such response back to the EC. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE: report by Lutz Schubert Date: Wed, 2 Oct 2013 15:37:43 +0000 From: To: , , CC: , Dear Juanjo, As indicated before, the assessment of prototypes during FI-WARE reviews is mostly based on the demos. I would like to have a better assessment of the prototypes, independent from the normal FI-WARE reviews. Therefore, Lutz Schubert from the University of Ulm (formerly with HLRS Stuttgart) has carried out this task. His report is attached. The report is the status as of 10 days ago, and might not be fully complete/consistent related to the Catalogue, the specifications of the wiki, etc. However, it does not make a lot of sense to try to perfect the assessment right now, as the report is clear of its main conclusions. A similar, second exercise could be done in (say) 6 months from now. Best regards, Arian ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Miguel Carrillo Subject: Update of GEi list Date: Tue, 20 Aug 2013 15:51:13 +0200 Size: 54090 URL: -------------- next part -------------- An embedded message was scrubbed... From: Miguel Carrillo Subject: Complete list of GE/GEis Date: Mon, 26 Aug 2013 18:45:55 +0200 Size: 50425 URL: From mcp at tid.es Tue Oct 8 19:37:28 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 08 Oct 2013 19:37:28 +0200 Subject: [Fiware-wpl] Forge maintenance on Friday afternoon + known problems on the forge Message-ID: <525442D8.9050201@tid.es> Dear all, Apparently we are experiencing some troubles on the forge due to the lack of disk space allocated to a fraction of the tools we are using. These operations will possibly fail so please defer them until Monday: * Uploading files to the "Files" tools * Uploading files to SVN Fortunately, the "Docs" tool and the wiki should work ok (the info is stored elsewhere) We will fix it next Friday. The platform will be down for a while: * Date: Friday, 11 * Start time: 16:00 CET * End time: 20:00 CET Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Oct 11 08:51:25 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 11 Oct 2013 08:51:25 +0200 Subject: [Fiware-wpl] VERY IMPORTANT AND URGENT: regarding evaluation of costs reports Message-ID: <52579FED.1040504@tid.es> Hi all, The EC has asked us to answer the following question during the process of evaluation of our costs report: We need to know for all withdrawing partners: * The GEis they were responsible for * Per GEi they were responsible for: * The availability of the GEi within the FI-PPP, after the withdrawal of the beneficiary * The amount of person months spent (split for year 1 and year 2) My understanding we have to document the answer with regard to the withdrawal by Ericsson and NSN-Hungary and NSN-Finland. Regarding NSN-Findland, they haven't reported any costs, so there is no impact. However, we need the answer to the above questions in the case of Ericsson and NSN-Hungary. Can the following WPLs provide the answer ? * Regarding Ericsson: * WP3 (Apps chapter) * WP9 (Tools chapter) * Regarding NSN-Hungary * WP5 (IoT chapter) We need this info urgently to close the reporting in NEF. Please provide it by Monday EOB. Better if today. If you believe there is any other case of withdrawal we are missing, please let me know. Thanks in advance, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri Oct 11 11:48:13 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 11 Oct 2013 09:48:13 +0000 Subject: [Fiware-wpl] VERY IMPORTANT AND URGENT: regarding evaluation of costs reports In-Reply-To: <52579FED.1040504@tid.es> References: <52579FED.1040504@tid.es> Message-ID: <1748_1381484894_5257C95E_1748_94_1_976A65C5A08ADF49B9A8523F7F81925C1162F7@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Juanjo, For Ericsson, they were responsible for Gateway Device Management GE and provided in R1 the Ericsson IoT Gateway (http://catalogue.fi-ware.eu/enablers/gateway-device-management-ge-ericsson-iot-gateway ); We expected to push it in open Source but did not reach a conclusion with Ericsson. For NSN, always in IoT chapter, they were responsible of Backend Device Management GE (no implementation provided because Cumulocity became a spin-off when they left) and also the Backend template Handler (which disappeared from the Architecture after they left) For the costs they claimed, I assume that Ercisson requested some costs for Year 2 till end of January 2012 but I do not know how many PM. And as far as I know NSN claimed mainly for year 1 and maybe resubmitted rejected costs from year 1 in year 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 11 octobre 2013 08:51 ? : fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] VERY IMPORTANT AND URGENT: regarding evaluation of costs reports Hi all, The EC has asked us to answer the following question during the process of evaluation of our costs report: We need to know for all withdrawing partners: * The GEis they were responsible for * Per GEi they were responsible for: * The availability of the GEi within the FI-PPP, after the withdrawal of the beneficiary * The amount of person months spent (split for year 1 and year 2) My understanding we have to document the answer with regard to the withdrawal by Ericsson and NSN-Hungary and NSN-Finland. Regarding NSN-Findland, they haven't reported any costs, so there is no impact. However, we need the answer to the above questions in the case of Ericsson and NSN-Hungary. Can the following WPLs provide the answer ? * Regarding Ericsson: * WP3 (Apps chapter) * WP9 (Tools chapter) * Regarding NSN-Hungary * WP5 (IoT chapter) We need this info urgently to close the reporting in NEF. Please provide it by Monday EOB. Better if today. If you believe there is any other case of withdrawal we are missing, please let me know. Thanks in advance, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Fri Oct 11 12:29:23 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Fri, 11 Oct 2013 12:29:23 +0200 Subject: [Fiware-wpl] VERY IMPORTANT AND URGENT: regarding evaluation of costs reports In-Reply-To: <52579FED.1040504@tid.es> References: <52579FED.1040504@tid.es> Message-ID: <5257D303.7060407@eng.it> Hi Juanjo, Ericsson in WP9 as contributed with the Catalogue: - The FI-WARE Catalogue is available within the FI-PPP and it's now in charge of UPM - the amount of PM spent for Y1: 13,37 and for Y2: 4,02 I've taken these numbers from the progress reports, but I don't know if these are the same reported by Ericsson in Form-C kind regards, Davide On 11/10/2013 08:51, Juanjo Hierro wrote: > Hi all, > > The EC has asked us to answer the following question during the > process of evaluation of our costs report: > > We need to know for all withdrawing partners: > > * The GEis they were responsible for > * Per GEi they were responsible for: > o The availability of the GEi within the FI-PPP, after the > withdrawal of the beneficiary > o The amount of person months spent (split for year 1 and > year 2) > > > My understanding we have to document the answer with regard to the > withdrawal by Ericsson and NSN-Hungary and NSN-Finland. Regarding > NSN-Findland, they haven't reported any costs, so there is no > impact. However, we need the answer to the above questions in the > case of Ericsson and NSN-Hungary. > > Can the following WPLs provide the answer ? > > * Regarding Ericsson: > o WP3 (Apps chapter) > o WP9 (Tools chapter) > * Regarding NSN-Hungary > o WP5 (IoT chapter) > > > We need this info urgently to close the reporting in NEF. Please > provide it by Monday EOB. Better if today. > > If you believe there is any other case of withdrawal we are missing, > please let me know. > > Thanks in advance, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > FI-PPP Architecture Board chairman > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 14 05:57:01 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Oct 2013 05:57:01 +0200 Subject: [Fiware-wpl] URGENT ACTIONS on Exploitation as outcome of the Y2 project review Message-ID: <525B6B8D.9090808@tid.es> Hi all, Find below my signature a draft of an email that I intend to deliver to the whole FI-WARE consortium, targeted to FI-WARE GEi owners, but I wish to share it with you first so that we can discuss it earlier in the follow-up confcall this morning and give it a final shape. It has to do with urgent action points regarding exploitation as outcome of the Y2 project review. I believe that we would comply with the requests made by the EC and reviewers regarding submission of exploitation plans if we follow the proposed action points. You will see that I refer to the month 30 review that the EC did request. I have exchanged a couple of mails with Arian very recently where it was clarified that one of the major goals of that review meeting is to review the request they have made regarding exploitation and, based on the response, take actions that may lead to discontinuation of the funding of some activities in some GEis which would be then assigned to "more promising" GEis. Talk to you later during our follow-up confcall. Please note that I may need to join a bit later, because I have to make a presentation on FI-WARE to a rather important visit. Best regards, -- Juanjo === Content of email Dear FI-WARE GEi owners, I hope that you have already had time to review the outcome and detailed report of the Y2 review. Despite generally speaking the results of the review are nice, there are a number of points that require immediate action and one of them has to do with exploitation plans by the FI-WARE GEi owners. You all know that the EC has always stated that external (i.e., beyond the FI-PPP) availability plans regarding FI-WARE GEis should be clear and publicly available. We have always responded that the place where external availability would be stated is the FI-WARE Catalogue (http://catalogue.fi-ware.eu). However, as pointed in [1], this commitment has not been fulfilled by the majority of GEis. On the other hand, the EC and reviewers clearly seem not to be satisfied by the confidential individual plans delivered by the partners (see [2]). They lack of references to the FI-WARE GEis owned by the individual partner submitting each of the exploitation plans. They stated that, with a few exceptions, those exploitation plans are weak, and also lack of positioning with respect to FI-WARE in general and FI-LAB in particular (at the point in which the review report was produced, still being referred as FI-WARE OIL). In order to cover these different issues, the EC has asked for a resubmission of the individual exploitation plans and the fixing of the situation in the Catalogue before end of October, which we ask you to handle the following way: 1. Fix the "External availability" section in the "Terms and Conditions" tab of each of the FI-WARE GEis you own. Don't forget to review the guidelines on contents of that section provided at: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Terms_and_Conditions 2. Produce a new confidential individual exploitation plan which should: * covers your general exploitation plan regarding FI-WARE, which should include a description of what is the role that FI-LAB plays in that plan * elaborates on the individual exploitation plans you have with respect to each of the FI-WARE GEis you own. Although this is not strictly required for the GEis that are made publicly available as open source, we also encourage you to elaborate on those as well, explaining what are your exploitation plans for them, or at least what are your commitments regarding support to the open source software. Note that failure to cover the several action points for a given FI-WARE GEi may lead to decision on discontinuation of that FI-WARE GEi in the project. The corresponding funding would then be reassigned to work in other GEis. It would be highly advisable that you take the opportunity to review that the entry linked to each of the FI-WARE GEis you own in the FI-WARE Catalogue follow the general guidelines provided in: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue Therefore, we ask you to work diligently addressing the above action points. Note that, regarding the Catalogue, this is not work that is new but should have been address long time ago (as pointed out by the reviewers) so it should not be that difficult. If your exploitation plans are clear enough as they should be at this point in the project, updating the individual exploitation plans accordingly should also not be a big issue and sharing it confidentially with the EC and reviewers shouldn't be also. Whenever you update the "External availability" section in the "Terms and Conditions" part of a given FI-WARE GEi in the Catalogue, please send an email notifying this circumstance to Juan Bare?o and copy your WPL, Miguel Carrillo and me . Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 14 06:09:13 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Oct 2013 06:09:13 +0200 Subject: [Fiware-wpl] Fwd: URGENT ACTIONS on Exploitation as outcome of the Y2 project review In-Reply-To: <525B6B8D.9090808@tid.es> References: <525B6B8D.9090808@tid.es> Message-ID: <525B6E69.4040604@tid.es> I forgot to include the references. I have added them at the end of this message. -------- Original Message -------- Subject: URGENT ACTIONS on Exploitation as outcome of the Y2 project review Date: Mon, 14 Oct 2013 05:57:01 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, Find below my signature a draft of an email that I intend to deliver to the whole FI-WARE consortium, targeted to FI-WARE GEi owners, but I wish to share it with you first so that we can discuss it earlier in the follow-up confcall this morning and give it a final shape. It has to do with urgent action points regarding exploitation as outcome of the Y2 project review. I believe that we would comply with the requests made by the EC and reviewers regarding submission of exploitation plans if we follow the proposed action points. You will see that I refer to the month 30 review that the EC did request. I have exchanged a couple of mails with Arian very recently where it was clarified that one of the major goals of that review meeting is to review the request they have made regarding exploitation and, based on the response, take actions that may lead to discontinuation of the funding of some activities in some GEis which would be then assigned to "more promising" GEis. Talk to you later during our follow-up confcall. Please note that I may need to join a bit later, because I have to make a presentation on FI-WARE to a rather important visit. Best regards, -- Juanjo === Content of email Dear FI-WARE GEi owners, I hope that you have already had time to review the outcome and detailed report of the Y2 review. Despite generally speaking the results of the review are nice, there are a number of points that require immediate action and one of them has to do with exploitation plans by the FI-WARE GEi owners. You all know that the EC has always stated that external (i.e., beyond the FI-PPP) availability plans regarding FI-WARE GEis should be clear and publicly available. We have always responded that the place where external availability would be stated is the FI-WARE Catalogue (http://catalogue.fi-ware.eu). However, as pointed in [1], this commitment has not been fulfilled by the majority of GEis. On the other hand, the EC and reviewers clearly seem not to be satisfied by the confidential individual plans delivered by the partners (see [2]). They lack of references to the FI-WARE GEis owned by the individual partner submitting each of the exploitation plans. They stated that, with a few exceptions, those exploitation plans are weak, and also lack of positioning with respect to FI-WARE in general and FI-LAB in particular (at the point in which the review report was produced, still being referred as FI-WARE OIL). In order to cover these different issues, the EC has asked for a resubmission of the individual exploitation plans and the fixing of the situation in the Catalogue before end of October, which we ask you to handle the following way: 1. Fix the "External availability" section in the "Terms and Conditions" tab of each of the FI-WARE GEis you own. Don't forget to review the guidelines on contents of that section provided at: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Terms_and_Conditions 2. Produce a new confidential individual exploitation plan which should: * covers your general exploitation plan regarding FI-WARE, which should include a description of what is the role that FI-LAB plays in that plan * elaborates on the individual exploitation plans you have with respect to each of the FI-WARE GEis you own. Although this is not strictly required for the GEis that are made publicly available as open source, we also encourage you to elaborate on those as well, explaining what are your exploitation plans for them, or at least what are your commitments regarding support to the open source software. Note that failure to cover the several action points for a given FI-WARE GEi may lead to decision on discontinuation of that FI-WARE GEi in the project. The corresponding funding would then be reassigned to work in other GEis. It would be highly advisable that you take the opportunity to review that the entry linked to each of the FI-WARE GEis you own in the FI-WARE Catalogue follow the general guidelines provided in: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue Therefore, we ask you to work diligently addressing the above action points. Note that, regarding the Catalogue, this is not work that is new but should have been address long time ago (as pointed out by the reviewers) so it should not be that difficult. If your exploitation plans are clear enough as they should be at this point in the project, updating the individual exploitation plans accordingly should also not be a big issue and sharing it confidentially with the EC and reviewers shouldn't be also. Whenever you update the "External availability" section in the "Terms and Conditions" part of a given FI-WARE GEi in the Catalogue, please send an email notifying this circumstance to Juan Bare?o and copy your WPL, Miguel Carrillo and me . Best regards, -- Juanjo [1] - From the Outcome of the review report (page 2): For the other 32 GE implementations, the Catalogue mentions that the terms and conditions for external availability are not defined yet, or that somebody had to be contacted. The latter may mean anything from available but not public, via to-be-negotiated, to unknown. It should be noted that the Commission had requested clarification on these terms and conditions for the first time following the first year review. Progress here is too slow. It should also be noted that the consortium nowadays publicly states that the majority of the GE implementation are open source. This obviously is not the impression one gets from the Catalogue. [2] - From the detailed review report: (page 4) - In line with the above requested: Exploitation of project results by FI-WARE partners The (lack of) substance and concreteness for the vast majority of the individual exploitation plans, at Month 24, is totally inappropriate for the ambition of FI-WARE and incommensurate with the claimed business commitment to project results by the main partners, even to Vice-President Kroes. As for the previous period, there is no visible attempt to echo - let alone apply - the well-elaborated business and ecosystem analysis to the individual partners' own approach and planning regarding project results. The reviewers are exceedingly concerned about the dearth of concrete evidence of the business commitment of GE implementation owners, and the corresponding lack of concrete information and traceability of GE implementations in the exploitation plans of these owners. (Page 50) - Feedback regarding Individual Exploitation plans: D11.2.2 Exploitation Plan, including IPR Management o Unfortunately, despite the repeated comments by the reviewers on this very subject, the specific company exploitation plans are still generic and in some cases bordering on being a "wish list". They all say positive things but lack specificity in themes, markets, applications, timeline, budget and resources dedicated to the success of FI-WARE. With a few exceptions such as those supplied by ATOS and Thales and to some extent Telefonica and France Telecom, the individual exploitation plans are largely a collection of wishes, expectations and high level aims o In all cases, there are surprisingly very few references to specific GEs (or GE combinations) even by the owners concerned. In addition, they are a collation of single plans without any attempt to explain which type of synchronisation or coordination will happen among them and how this concerted effort will be coordinated, if any. There is not a single reference in the individual plans to the OIL, which is positioned in the generic part of the document as a key vehicle to "pave the way for a successful exploitation and sustainability of its [the FI-WARE project] results". ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 14 06:59:07 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Oct 2013 06:59:07 +0200 Subject: [Fiware-wpl] Regarding re-submission of rejected deliverables Message-ID: <525B7A1B.80203@tid.es> Hi all, Regarding re-submission of rejected deliverables, or deliverables not submitted, following is my take: * D2.1.3 - FI-WARE Requirements Backlog (not submitted, no re-submission required) * D2.1.4 - FI-WARE Requirements Backlog (no re-submission required) * D2.1.5 - FI-WARE Requirements Backlog (no re-submission required) This is a sign that we have to be more serious with description of the backlog. We insist once more: looking at the backlog of each chapter in its tracker within a given month (matching a Sprint) it would be feasible to understand what every company in that chapter is doing. You should track all kind of activities through WorkItems as well as development activities (development of user-stories or at least refinement of Epics and Features). Note that the next (and theorically last) release of this deliverable is end of this month ! (with an extension of 4 months to the project, it may lead to definition of an additional release of the deliverable, but we should definitively be able to address this in this release) * D2.4.2 - FI-WARE Technical Roadmap (no re-submission required) Still analyzing the comments. However, my view on this is that the reviewers don't criticize the approach but point out several aspects in which there is actually a space of improvement: * The Technical Roadmap ends referring to the backlog, so that every weakness in the backlog propagates to the roadmap. In particular, there is a lack of detailed description for some features of several GEis (they are too high-level or vague) including non-functional features (e.g., it is stated that "mass provisioning of users" should be supported, but no target values are provided). There are also some inconsistencies found which has been reported by the reviewers. * Correlation with demands from UC projects. This proved to be unimplementable with phase 1 projects, but should improve in phase 2 with the implementation of the JIRA projects for each of the FI-WARE GEi. We may require UC projects to provide feedback through JIRA and, if not provided, at least we would have a justification for the lack of traceability with respect to requirements by UC projects (hopefully it won't be the case but UC projects will actually provide their feedback). * Cross-chapter Epic/Features and cross-GEis Epic/Features within a chapter should be captured * D2.5.2 - Third party innovation enablement in FI-WARE (not submitted, submission required after 1 month of the review report) We all know that this deliverable was not submitted because there was no one willing to lead the task of editing it. This is not acceptable. I expect proposals on the matter given the fact that this project is a cooperative project. * D2.6.2 - State of the Art Analysis - Emerging Technologies (no re-submission required) We have to carefully analyze the review report comments. It theory, there is plenty of time (next version of this deliverable is planned to be month 36, i.e., end of April 2014) but we should at least start discussion about how we will organize its development. * D8.1.2 - Security Chapter GE Open Specifications (re-submission required within 1 month of the receipt of the Review Report). I believe this re-submission is already being handled. * D9.1.3 - FI-CoDE Basic Framework (no re-submission required) * D9.2.2 - FI-CoDE Handbook (no re-submission required) * D9.3.2 - API IDE Support (no re-submission required) * D9.4.2 - Application Testing and Deployment Support (no re-submission required) Engineering should come with a plan here. They should provide an analysis of the comments and a concrete action plan about how to address those comments. * D10.5.2 - Report on Validation Process including Validation with Use Case projects (re-submission required within 1 month of the receipt of the Review Report). SAP already proposed an action plan so unless other feedback, we will stick to it. * D11.2.2 - Exploitation Plan, including IPR Management (re-submission required by Month 30) I have already shared with you my plan on how to address this re-submission. Nevertheless, we will review all this during our follow-up confcall today. Cheers, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Mon Oct 14 10:24:50 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 14 Oct 2013 08:24:50 +0000 Subject: [Fiware-wpl] Minutes and action points on validation deliverable submission (10.5.2b) Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664860552DD@DEWDFEMB11A.global.corp.sap> Dear colleagues, on Friday there was a testbed-internal session which discussed how to submit D.10.5.2b (the resubmission of the validation deliverable). We have a very tight schedule to submit this deliverable with all contributions in time. For this minutes I'm taking WPL/WPA on the CC list in order to let everybody know the status. Thorsten presented the approach and explained along the lines of the presentation what content should needs to be produced. - Mainly the testbed-team will in a neutral way write what we "see", judged by the numbers - things like: "SMARTAGRIFOOD rated the integration badly in the case of the XXX chapter...." We could try to come up with first assumptions on why these ratings did take place and dig deeper - but overall WPL/WPA need to do the _content_ driven analysis. "The reason for this was ..." or "We will take this serious and already implemented the following actions ..." Background are the graphs and tables prepared by Thorsten in the presentation and pivot-tables of the XLS. - Additionally and for the deliverable the "scenario based" questionnairs in DOC format need to be analyzed and "highs" and "lows" need to be extracted for the chapters. - Stefano wanted everybody to analyze the bare-metal XLS and try to come up with "new interesting" things somebody sees in the day. This task needs to be worked on in parallel within the week of 14.10. - 18.10. - everybody to report relevant findings on the 22.10. Rough time plan: KW42 (14.-18.10): main content work, Testbed-team writing what we "see", judged by the numbers KW43 (21.-25.10): finalizing text & hand-over to WPL/WPA team - 22th of October: deadline for the content work - goal: on 23th October WPL/WPA should be able to start their work with the content analysis (you will have ~3 business days) KW44 (28.-30.10): finalizing the DOC deliverable and starting a review cycle - Please volunteer if you want to be a reviewer for this deliverable KW44 (31.10): planned submission to EC Please - if possible - directly update the wiki on https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/The_Validation_Analysis or the underlying pages. If unsure, just write the text in any other format and provide it ASAP to Thorsten so he can integrated it to the wiki. Find attached the updated presentation & the bare-metal data in XLS format. Assignments for writing the Analysis: - Cloud-chapter: John - Data: Clara - IoT: Salvatore - Overall FI-WARE: Stefano - Methodologie: Thorsten - Open chapters: o Apps o Security (ask Pascal) o Use Case chapters (all of them not assigned) Any questions or corrections, please let me know /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2013-10-07-FI-WARE_validation_analysis.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 1194299 bytes Desc: 2013-10-07-FI-WARE_validation_analysis.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2013-10-07-validation-answers-to-validation-questionnaire-phase-one_updated_september.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 180147 bytes Desc: 2013-10-07-validation-answers-to-validation-questionnaire-phase-one_updated_september.xlsx URL: From jhierro at tid.es Mon Oct 14 10:48:50 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Oct 2013 10:48:50 +0200 Subject: [Fiware-wpl] Delay start of the confcall Message-ID: <525BAFF2.1050408@tid.es> Hi all, I need to delay the start of our confcall half an hour. Please connect at 11:30. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 14 11:27:15 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Oct 2013 11:27:15 +0200 Subject: [Fiware-wpl] Link to pre-minutes of the WPLs/WPAs follow-up confcall today Message-ID: <525BB8F3.1080108@tid.es> Hi all, Please find here the link to the pre-minutes of our confcall today: https://docs.google.com/document/d/1oFEnpgRVR1AF4zy2L8pK-8n4BJZLn4O57e5wJTsjq2s/edit?usp=sharing Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 14 12:49:30 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Oct 2013 12:49:30 +0200 Subject: [Fiware-wpl] confcall this afternoon Message-ID: <525BCC3A.9020708@tid.es> Hi all, The afternoon session today will be devoted to continue discussion on re-submission of deliverables. However, we will start at 14:00 as just discussed. Regarding follow-up of the IdM task force, Pascal will drop an email suggesting to meet at 11:00am tomorrow. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Oct 14 12:55:45 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 14 Oct 2013 12:55:45 +0200 Subject: [Fiware-wpl] TR: FI-WARE IdM GE Task Force audio rescheduled to 15/10. Message-ID: <3913_1381748148_525BCDB3_3913_6983_1_CBBCD6C304123F4AB23FAAE3055C8C0E02081F8880A5@THSONEA01CMS04P.one.grp> FYI De : BISSON Pascal Envoy? : lundi 14 octobre 2013 12:55 ? : fiware-idm-ge at lists.fi-ware.eu Cc : BISSON Pascal; GIDOIN Daniel; DANGERVILLE Cyril; Juanjo Hierro Objet : FI-WARE IdM GE Task Force audio rescheduled to 15/10. Importance : Haute Dear IdM GE Task Force Colleagues, This email just to let you know that our audio conference on IdM GE task force initially anticipated this afternoon (at 2:30) has been rescheduled to tomorrow so 15/10 at 11am. This as per decision taken this morning at WPL/WPA Audio conf. Details to join remains unchanged. Apologize for the inconvenience and YES take necessary steps to attend or be represented. Objective would be here to report on status what has been done and what remains to be done being said deadline for IdM GE Open Specs (and Open APIs ) remains unchanged (end of the month) and we'd like to go for a review at Chapter and Project management level. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 14 15:32:25 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Oct 2013 15:32:25 +0200 Subject: [Fiware-wpl] URGENT ACTIONS on Exploitation as outcome of the Y2 project review In-Reply-To: <525B6B8D.9090808@tid.es> References: <525B6B8D.9090808@tid.es> Message-ID: <525BF269.6090208@tid.es> Dear FI-WARE GEi owners, I hope that you have already had time to review the outcome and detailed report of the Y2 review. Despite generally speaking the results of the review are nice, there are a number of points that require immediate action and one of them has to do with exploitation plans by the FI-WARE GEi owners. You all know that the EC has always stated that external (i.e., beyond the FI-PPP) availability plans regarding FI-WARE GEis should be clear and publicly available. We have always responded that the place where external availability would be stated is the FI-WARE Catalogue (http://catalogue.fi-ware.eu). However, as pointed in [1], this commitment has not been fulfilled by the majority of GEis. On the other hand, the EC and reviewers clearly seem not to be satisfied by the confidential individual plans delivered by the partners (see [2]). They lack of references to the FI-WARE GEis owned by the individual partner submitting each of the exploitation plans. They stated that, with a few exceptions, those exploitation plans are weak, and also lack of positioning with respect to FI-WARE in general and FI-LAB in particular (at the point in which the review report was produced, still being referred as FI-WARE OIL). In order to cover these different issues, the EC has asked for a resubmission of the individual exploitation plans and the fixing of the situation in the Catalogue before end of October, which we ask you to handle the following way: 1. Fix the "External availability" section in the "Terms and Conditions" tab of each of the FI-WARE GEis you own. Don't forget to review the guidelines on contents of that section provided at: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Terms_and_Conditions 2. Produce a new confidential individual exploitation plan which should: * covers your general exploitation plan regarding FI-WARE, which should include a description of what is the role that FI-LAB plays in that plan * elaborates on the individual exploitation plans you have with respect to each of the FI-WARE GEis you own. Although this is not strictly required for the GEis that are made publicly available as open source, we also encourage you to elaborate on those as well, explaining what are your exploitation plans for them, or at least what are your commitments regarding support to the open source software. Note that failure to cover the several action points for a given FI-WARE GEi may lead to a decision by the EC on discontinuation of that FI-WARE GEi in the project. The corresponding funding would then be then reassigned to work in other GEis, they say (see [3]). It would be highly advisable that you take the opportunity to review that the entry linked to each of the FI-WARE GEis you own in the FI-WARE Catalogue follow the general guidelines provided in (instead of just fixing the section on "External availability"): http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue Therefore, we ask you to work diligently addressing the above action points. Note that, regarding the Catalogue, this is not work that is new but should have been address long time ago (as pointed out by the reviewers) so it should not be that difficult. If your exploitation plans are clear enough as they should be at this point in the project, updating the individual exploitation plans accordingly should also not be a big issue and sharing it confidentially with the EC and reviewers shouldn't be also. Whenever you update the "External availability" section in the "Terms and Conditions" part of a given FI-WARE GEi in the Catalogue, or you send your individual exploitation plans to the EC, please send an email notifying this circumstance to Juan Bare?o and copy your WPL, Miguel Carrillo and me . Best regards, -- Juanjo [1] - From the Outcome of the review report (page 2): For the other 32 GE implementations, the Catalogue mentions that the terms and conditions for external availability are not defined yet, or that somebody had to be contacted. The latter may mean anything from available but not public, via to-be-negotiated, to unknown. It should be noted that the Commission had requested clarification on these terms and conditions for the first time following the first year review. Progress here is too slow. It should also be noted that the consortium nowadays publicly states that the majority of the GE implementation are open source. This obviously is not the impression one gets from the Catalogue. [2] - From the detailed review report: (page 4) - In line with the above requested: Exploitation of project results by FI-WARE partners The (lack of) substance and concreteness for the vast majority of the individual exploitation plans, at Month 24, is totally inappropriate for the ambition of FI-WARE and incommensurate with the claimed business commitment to project results by the main partners, even to Vice-President Kroes. As for the previous period, there is no visible attempt to echo - let alone apply - the well-elaborated business and ecosystem analysis to the individual partners' own approach and planning regarding project results. The reviewers are exceedingly concerned about the dearth of concrete evidence of the business commitment of GE implementation owners, and the corresponding lack of concrete information and traceability of GE implementations in the exploitation plans of these owners. (Page 50) - Feedback regarding Individual Exploitation plans: D11.2.2 Exploitation Plan, including IPR Management o Unfortunately, despite the repeated comments by the reviewers on this very subject, the specific company exploitation plans are still generic and in some cases bordering on being a "wish list". They all say positive things but lack specificity in themes, markets, applications, timeline, budget and resources dedicated to the success of FI-WARE. With a few exceptions such as those supplied by ATOS and Thales and to some extent Telefonica and France Telecom, the individual exploitation plans are largely a collection of wishes, expectations and high level aims o In all cases, there are surprisingly very few references to specific GEs (or GE combinations) even by the owners concerned. In addition, they are a collation of single plans without any attempt to explain which type of synchronisation or coordination will happen among them and how this concerted effort will be coordinated, if any. There is not a single reference in the individual plans to the OIL, which is positioned in the generic part of the document as a key vehicle to "pave the way for a successful exploitation and sustainability of its [the FI-WARE project] results". [3] - From the outcome of the review report (page 3): The received or latest exploitation plans will be evaluated. Use of the respective GE implementations by the phase 2 use case projects will also be considered. The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Mon Oct 14 21:28:07 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 14 Oct 2013 21:28:07 +0200 Subject: [Fiware-wpl] catalogue status Message-ID: dear all, attached the Excel file i promised during our confcall of this morning. it in fact includes two aspects as there is also a column providing the status of "terms and condition - exernal availability". you can evaluate by yourself the situation and who is the bottlneck (@markus apologises if this morning i was a bit aggressive, but there are no pending tasks on the quality check team ....), still i think i need to be the lock, as there was at least one ge published which should not be (and indeed i unpublished it) and some others that really worries me. in most cases the situation is still not nice to say the least and in my opinion it should be clarified in the coming days NOT weeks. if the wpls go directly in the catalogue will also see that several of the ges do not refer to the last version (again lutz cannot be blamed here ...). in addition you'll see that there are several dummy entries which for cleaness i suggest to delete (at least doing this will facilitate the quality check work). about" terms and conditions" the situation at the moment is clearly not positive. i'd like to remind you that whatever you think, the catalogue is the real marketing acces to fi-ware and keeping in this state is not worth and above all not effective for the its purpose. i think it should be improved also from its graphical aspect and usability, but this is another story. @juanjo: perhaps we should make an announcement about the current geis global availability, i think in the last announcement some now available were not mentioned. ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- A non-text attachment was scrubbed... Name: Testbed-V2_catalogue_publication_status.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 19151 bytes Desc: not available URL: From jhierro at tid.es Tue Oct 15 06:32:59 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 15 Oct 2013 06:32:59 +0200 Subject: [Fiware-wpl] URGENT ACTIONS on Exploitation as outcome of the Y2 project review In-Reply-To: <525BF269.6090208@tid.es> References: <525B6B8D.9090808@tid.es> <525BF269.6090208@tid.es> Message-ID: <525CC57B.20206@tid.es> Hi again, A clarification on my previous mail. According to the outcome of the Y2 review report: "Organisations that joined the consortium as a result of a competitive call for additional beneficiaries and their GE implementations are excluded". The defined urgent actions therefore will not apply to new beneficiaries from the Open Call 2 and their corresponding GE implementations. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 14/10/13 15:32, Juanjo Hierro wrote: Dear FI-WARE GEi owners, I hope that you have already had time to review the outcome and detailed report of the Y2 review. Despite generally speaking the results of the review are nice, there are a number of points that require immediate action and one of them has to do with exploitation plans by the FI-WARE GEi owners. You all know that the EC has always stated that external (i.e., beyond the FI-PPP) availability plans regarding FI-WARE GEis should be clear and publicly available. We have always responded that the place where external availability would be stated is the FI-WARE Catalogue (http://catalogue.fi-ware.eu). However, as pointed in [1], this commitment has not been fulfilled by the majority of GEis. On the other hand, the EC and reviewers clearly seem not to be satisfied by the confidential individual plans delivered by the partners (see [2]). They lack of references to the FI-WARE GEis owned by the individual partner submitting each of the exploitation plans. They stated that, with a few exceptions, those exploitation plans are weak, and also lack of positioning with respect to FI-WARE in general and FI-LAB in particular (at the point in which the review report was produced, still being referred as FI-WARE OIL). In order to cover these different issues, the EC has asked for a resubmission of the individual exploitation plans and the fixing of the situation in the Catalogue before end of October, which we ask you to handle the following way: 1. Fix the "External availability" section in the "Terms and Conditions" tab of each of the FI-WARE GEis you own. Don't forget to review the guidelines on contents of that section provided at: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Terms_and_Conditions 2. Produce a new confidential individual exploitation plan which should: * covers your general exploitation plan regarding FI-WARE, which should include a description of what is the role that FI-LAB plays in that plan * elaborates on the individual exploitation plans you have with respect to each of the FI-WARE GEis you own. Although this is not strictly required for the GEis that are made publicly available as open source, we also encourage you to elaborate on those as well, explaining what are your exploitation plans for them, or at least what are your commitments regarding support to the open source software. Note that failure to cover the several action points for a given FI-WARE GEi may lead to a decision by the EC on discontinuation of that FI-WARE GEi in the project. The corresponding funding would then be then reassigned to work in other GEis, they say (see [3]). It would be highly advisable that you take the opportunity to review that the entry linked to each of the FI-WARE GEis you own in the FI-WARE Catalogue follow the general guidelines provided in (instead of just fixing the section on "External availability"): http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue Therefore, we ask you to work diligently addressing the above action points. Note that, regarding the Catalogue, this is not work that is new but should have been address long time ago (as pointed out by the reviewers) so it should not be that difficult. If your exploitation plans are clear enough as they should be at this point in the project, updating the individual exploitation plans accordingly should also not be a big issue and sharing it confidentially with the EC and reviewers shouldn't be also. Whenever you update the "External availability" section in the "Terms and Conditions" part of a given FI-WARE GEi in the Catalogue, or you send your individual exploitation plans to the EC, please send an email notifying this circumstance to Juan Bare?o and copy your WPL, Miguel Carrillo and me . Best regards, -- Juanjo [1] - From the Outcome of the review report (page 2): For the other 32 GE implementations, the Catalogue mentions that the terms and conditions for external availability are not defined yet, or that somebody had to be contacted. The latter may mean anything from available but not public, via to-be-negotiated, to unknown. It should be noted that the Commission had requested clarification on these terms and conditions for the first time following the first year review. Progress here is too slow. It should also be noted that the consortium nowadays publicly states that the majority of the GE implementation are open source. This obviously is not the impression one gets from the Catalogue. [2] - From the detailed review report: (page 4) - In line with the above requested: Exploitation of project results by FI-WARE partners The (lack of) substance and concreteness for the vast majority of the individual exploitation plans, at Month 24, is totally inappropriate for the ambition of FI-WARE and incommensurate with the claimed business commitment to project results by the main partners, even to Vice-President Kroes. As for the previous period, there is no visible attempt to echo - let alone apply - the well-elaborated business and ecosystem analysis to the individual partners' own approach and planning regarding project results. The reviewers are exceedingly concerned about the dearth of concrete evidence of the business commitment of GE implementation owners, and the corresponding lack of concrete information and traceability of GE implementations in the exploitation plans of these owners. (Page 50) - Feedback regarding Individual Exploitation plans: D11.2.2 Exploitation Plan, including IPR Management o Unfortunately, despite the repeated comments by the reviewers on this very subject, the specific company exploitation plans are still generic and in some cases bordering on being a "wish list". They all say positive things but lack specificity in themes, markets, applications, timeline, budget and resources dedicated to the success of FI-WARE. With a few exceptions such as those supplied by ATOS and Thales and to some extent Telefonica and France Telecom, the individual exploitation plans are largely a collection of wishes, expectations and high level aims o In all cases, there are surprisingly very few references to specific GEs (or GE combinations) even by the owners concerned. In addition, they are a collation of single plans without any attempt to explain which type of synchronisation or coordination will happen among them and how this concerted effort will be coordinated, if any. There is not a single reference in the individual plans to the OIL, which is positioned in the generic part of the document as a key vehicle to "pave the way for a successful exploitation and sustainability of its [the FI-WARE project] results". [3] - From the outcome of the review report (page 3): The received or latest exploitation plans will be evaluated. Use of the respective GE implementations by the phase 2 use case projects will also be considered. The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Tue Oct 15 14:54:55 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 15 Oct 2013 12:54:55 +0000 Subject: [Fiware-wpl] FYI My vacation from 16.-27. October 2013 Message-ID: <393554EDCF801348BC53C7813C6CB73B1A67F0BD@DEWDFEMB14A.global.corp.sap> Hi all, FYI I am on vacation from 16.-27. October 2013 and will return to my office on 28.10. Torsten Leidig will take over the Apps chapter matters during my vacation. Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdps at tid.es Tue Oct 15 15:39:56 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Tue, 15 Oct 2013 13:39:56 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) Message-ID: <77A22C1085494D48B4018F06A40DB2C72FFBE1AE@EX10-MB2-MAD.hi.inet> Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: [cid:image001.png at 01CEBE9E.1EC99280] So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 45089 bytes Desc: image002.jpg URL: From jdps at tid.es Wed Oct 16 08:05:26 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 16 Oct 2013 06:05:26 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) Message-ID: <77A22C1085494D48B4018F06A40DB2C72FFBFD9A@EX10-MB2-MAD.hi.inet> Dear all. I'm sorry because there is a mistake in the deadline. Deadline: October 30th 2013. (Not November as I said by mistake) Thank you. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: martes, 15 de octubre de 2013 15:40 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: [cid:image001.png at 01CEBE9E.1EC99280] So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 45089 bytes Desc: image001.jpg URL: From jdps at tid.es Wed Oct 16 12:01:14 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 16 Oct 2013 10:01:14 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) Message-ID: <77A22C1085494D48B4018F06A40DB2C72FFC0BBE@EX10-MB2-MAD.hi.inet> Hi again, I'm sure that you know it, but to avoid misunderstandings, please let me tell you that: Periodic Report M30 starts on May 2013 (M25) and ends on October 2013 (M30). BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: mi?rcoles, 16 de octubre de 2013 8:05 Para: 'fiware-wpl at lists.fi-ware.eu'; fiware-wpa at lists.fi-ware.eu CC: 'subsidies at tid.es' Asunto: RE: FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all. I'm sorry because there is a mistake in the deadline. Deadline: October 30th 2013. (Not November as I said by mistake) Thank you. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: martes, 15 de octubre de 2013 15:40 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: [cid:image001.png at 01CEBE9E.1EC99280] So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 45089 bytes Desc: image001.jpg URL: From juan.bareno at atos.net Thu Oct 17 16:41:11 2013 From: juan.bareno at atos.net (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Thu, 17 Oct 2013 16:41:11 +0200 Subject: [Fiware-wpl] FW: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 In-Reply-To: <77A22C1085494D48B4018F06A40DB2C72FFBE364@EX10-MB2-MAD.hi.inet> References: <77A22C1085494D48B4018F06A40DB2C72FFBE364@EX10-MB2-MAD.hi.inet> Message-ID: Dear Exploitation Colleagues 1. Progress report: request for contributions 2. Periodic Report M30 starts on May 2013 (M25) and ends on October 2013 (M30). 3. Each partner fulfill its participation in each Task a. 11.1 Market Analysis- nothing new since the last M24 Deliverable b. 11.2 Exploitation- The Individual Confidential Exploitation Plans after the review and the ones requested for M30 c. 11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe the CONCORD meetings d. 11.4 Standardization- Lindsay?? e. 11.5 Community Building- Javier?? 4. Deadline next Friday 25th October Thanks for your support Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: JAVIER DE PEDRO SANCHEZ [mailto:jdps at tid.es] Sent: martes, 15 de octubre de 2013 15:56 To: Juan Bare?o Guerenabarrena Cc: subsidies at tid.es Subject: RE: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Hola Juan Te remito la plantilla del WP11. Cada socio debe ser evaluado por a nivel de tarea. Por favor, conf?rmame que te ha llegado ?ste correo. Gracias mil. Salu2. Javier. De: subsidies-bounces at tid.es [mailto:subsidies-bounces at tid.es] En nombre de JAVIER DE PEDRO SANCHEZ Enviado el: martes, 15 de octubre de 2013 15:40 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: [Subsidies] FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 45089 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 339 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 4064 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.1.2.5 - WP11.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 225966 bytes Desc: D.1.2.5 - WP11.docx URL: From javier.devicente at futuranetworks.com Thu Oct 17 20:01:03 2013 From: javier.devicente at futuranetworks.com (Javier de Vicente) Date: Thu, 17 Oct 2013 20:01:03 +0200 Subject: [Fiware-wpl] FW: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 In-Reply-To: References: <77A22C1085494D48B4018F06A40DB2C72FFBE364@EX10-MB2-MAD.hi.inet> Message-ID: <526025DF.4000703@futuranetworks.com> Dear Juan, all, Sure you can count on us for the 11.5 part. Thanks a lot, Javier -- Javier de Vicente Corporate & Government Affairs Futura Networks, S.L. Av. de Atenas 10 28290, Las Rozas, Madrid ? Spain phone: +34 910808353 skype: fjaviervicente http://www.campus-party.org El 17/10/13 16:41, Juan Bare?o Guerenabarrena escribi?: > > Dear Exploitation Colleagues > > 1.Progress report: request for contributions > > 2.Periodic Report M30 starts on May 2013 (M25) and ends on October > 2013 (M30). > > 3.Each partner fulfill its participation in each Task > > a.11.1 Market Analysis- nothing new since the last M24 Deliverable > > b.11.2 Exploitation- The Individual Confidential Exploitation Plans > after the review and the ones requested for M30 > > c.11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe > the CONCORD meetings > > d.11.4 Standardization- Lindsay?? > > e.11.5 Community Building- Javier?? > > 4.Deadline next Friday 25^th October > > Thanks for your support > > Juan > > Description: cid:image001.png at 01CC3A4E.0D917B80 > > *Juan Bare?o* > > Group Innovation, Business Development & Strategy > > Research & Innovation > > +34 912148859 > > Calle Albarrac?n 25, 28037 Madrid > > juan.bareno at atos.net > > www.atos.net > > **Description: Atos_Olympic_Games_Logo[1]** > > *IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail > address juan.bareno at atos.net .The former > @atosresearch.eu address will be cancelled soon* > > *From:*JAVIER DE PEDRO SANCHEZ [mailto:jdps at tid.es] > *Sent:* martes, 15 de octubre de 2013 15:56 > *To:* Juan Bare?o Guerenabarrena > *Cc:* subsidies at tid.es > *Subject:* RE: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 > *Importance:* High > > Hola Juan > > Te remito la plantilla del WP11. Cada socio debe ser evaluado por a > nivel de tarea. > > Por favor, conf?rmame que te ha llegado ?ste correo. > > Gracias mil. > > Salu2. > > Javier. > > *De:*subsidies-bounces at tid.es > [mailto:subsidies-bounces at tid.es] *En nombre de *JAVIER DE PEDRO SANCHEZ > *Enviado el:* martes, 15 de octubre de 2013 15:40 > *Para:* 'fiware-wpl at lists.fi-ware.eu' > *CC:* subsidies at tid.es > *Asunto:* [Subsidies] FI-WARE: Periodic Report M30 (D.1.2.5) > *Importancia:* Alta > > Dear all, as WPL, I need your contribution to deliver the Periodic > Report of M30. > > We have updated the template due to the following remark of the > Commission: > > cid:image001.png at 01CEBE9E.1EC99280 > > So, It is very important that the report shows the contribution of > each involved partner at task level. > > We kindly ask you to follow the template where the first section is > about the WP as a team, and each task is evaluated by partner. > > I?m going to send in a particularized e-mail with the template of your > WP to you. > > Please ask to each involved partner their information. > > As soon as I have the consumption of PM of each partner, I?ll send it > to you. > > Note: xxx= Missing information in the document. > > *Deadline: November 30^th 2013.* > > It is probably that we?ll need a new iteration after this deadline > with the effort of each partner, where we?ll need you to evaluate each > declaration of effort. > > Thank you in advance. > > BR > > Javier. > > ------------------------------------------------------------------------ > > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > ------------------------------------------------------------------ > 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 endeavours 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 informacion > confidencial > destinada solamente a la(s) persona(s) mencionadas anteriormente > pueden estar protegidos por secreto profesional. > Si usted recibe este correo electronico 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 > ningun > compromiso para el grupo Atos, salvo ratificacion escrita por ambas > partes. > Aunque se esfuerza al maximo por mantener su red libre de virus, el > emisor > no puede garantizar nada al respecto y no sera responsable de > cualesquiera > danos que puedan resultar de una transmision de virus. > ------------------------------------------------------------------ -- Javier de Vicente Corporate & Government Affairs Futura Networks, S.L. Av. de Atenas 10 28290, Las Rozas, Madrid ? Spain phone: +34 910808353 skype: fjaviervicente http://www.campus-party.org From Lindsay.Frost at neclab.eu Thu Oct 17 22:58:41 2013 From: Lindsay.Frost at neclab.eu (Lindsay Frost) Date: Thu, 17 Oct 2013 20:58:41 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 "Standardisation has become labeled as Exploitation?" Message-ID: <58967817BA9AEA4E92A38F89CE2EA932552730C2@DAPHNIS.office.hd> Dear Juan, dear all, I am surprised that Standardisation has become labeled as Exploitation. Do I understand right? The fact of the situation is that FIWARE is not "exploiting" standardization. Filling in the sheet below will not be easy for Partners, because (as you all know) there is no forward-planning for standardization, so there is no "main progress, main deviation, corrective action". The deliverables so far have all basically just reported what Partners did in SDOs. That is the factual situation. "Post hoc" activity reports. I am willing to help fill in the sheet below somehow, but I will need each and every partner (who as you know are not paid to do SDO work) to send me information basically like this: Our company XYZ is working mainly in WP n and m, where we consider the key standards where we can contribute to be a, b, c. Accordingly, we have for the last year been working on xxxxxx in order to zzzzzzz. The main result(s) so far have been 1111, 2222, 3333. /We are satisfied/We see a need to .../We have stopped ..../ (pick one) and will therefore in the next period or reporting do /nothing/something/... /(explain one). Do you (all) consider this a reasonable approach, with a likelihood of success? Or should I just write a paragraph of text explaining that "Standardisation is not an Exploitation activity" ? Thank you for your guidance, Lindsay SHEET TO BE FILLED IN, COPIED FROM THE WORD DOCUMENT SENT BY JUAN 1.1.1.1 Task 11.4: Contribution to Standardisation The objective of this task 11.4 is xxx. The breakdown of the contribution (please describe the main progress, main result, main deviation and main proposed corrective action) of each partner in this task 11.4 is: * 01-TID: xxx. * 02-SAP: xxx. * 03-IBM-IL: xxx. * 05-THALES: xxx. * 06-TI: xxx. * 07-FT: xxx. * 11-DT: xxx. * 16-ALU-I: xxx. * 17-ALU-D: xxx. * 18-SIEMENS: xxx. * 19-INTEL: xxx. * 20-NEC: xxx. * 29-DFKI: xxx. * 31-EPROS: xxx. * 32-IMINDS: xxx. From: Juan Bare?o Guerenabarrena [mailto:juan.bareno at atos.net] Sent: Donnerstag, 17. Oktober 2013 16:41 To: fiware-exploitation at lists.fi-ware.eu; fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: nuria.delama at atos.net; Lindsay Frost; javier.devicente at futuranetworks.com; mcp at tid.es; jdps at tid.es Subject: FW: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Dear Exploitation Colleagues 1. Progress report: request for contributions 2. Periodic Report M30 starts on May 2013 (M25) and ends on October 2013 (M30). 3. Each partner fulfill its participation in each Task a. 11.1 Market Analysis- nothing new since the last M24 Deliverable b. 11.2 Exploitation- The Individual Confidential Exploitation Plans after the review and the ones requested for M30 c. 11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe the CONCORD meetings d. 11.4 Standardization- Lindsay?? e. 11.5 Community Building- Javier?? 4. Deadline next Friday 25th October Thanks for your support Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: JAVIER DE PEDRO SANCHEZ [mailto:jdps at tid.es] Sent: martes, 15 de octubre de 2013 15:56 To: Juan Bare?o Guerenabarrena Cc: subsidies at tid.es Subject: RE: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Hola Juan Te remito la plantilla del WP11. Cada socio debe ser evaluado por a nivel de tarea. Por favor, conf?rmame que te ha llegado ?ste correo. Gracias mil. Salu2. Javier. De: subsidies-bounces at tid.es [mailto:subsidies-bounces at tid.es] En nombre de JAVIER DE PEDRO SANCHEZ Enviado el: martes, 15 de octubre de 2013 15:40 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: [Subsidies] FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: [cid:image001.png at 01CEBE9E.1EC99280] So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 339 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 4064 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 45089 bytes Desc: image004.jpg URL: From thorsten.sandfuchs at sap.com Fri Oct 18 18:12:41 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 18 Oct 2013 16:12:41 +0000 Subject: [Fiware-wpl] [Fiware-wpa] Minutes and action points on validation deliverable submission (10.5.2b) In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664860552DD@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664860552DD@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6648605BD90@DEWDFEMB11A.global.corp.sap> Dear colleagues, please find attached the first draft of the deliverable D.10.5.2b with early version of the content. - Salvatore provided already his part - John wanted to submit until Monday - For apps I wrote the text - For subsequent subchapters there is still a lot of content contributions open - happy for any contributions, either in the wiki or directly in the word file (please use "track-changes") We seem to fall behind the initial plan of finalizing the content within this week. Please try to contribute to the content ASAP in order to not require to shift the time plan or lose the ability to make a thorough review. Wish all of you a nice weekend & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Montag, 14. Oktober 2013 10:25 To: fiware-testbed at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Minutes and action points on validation deliverable submission (10.5.2b) Dear colleagues, on Friday there was a testbed-internal session which discussed how to submit D.10.5.2b (the resubmission of the validation deliverable). We have a very tight schedule to submit this deliverable with all contributions in time. For this minutes I'm taking WPL/WPA on the CC list in order to let everybody know the status. Thorsten presented the approach and explained along the lines of the presentation what content should needs to be produced. - Mainly the testbed-team will in a neutral way write what we "see", judged by the numbers - things like: "SMARTAGRIFOOD rated the integration badly in the case of the XXX chapter...." We could try to come up with first assumptions on why these ratings did take place and dig deeper - but overall WPL/WPA need to do the _content_ driven analysis. "The reason for this was ..." or "We will take this serious and already implemented the following actions ..." Background are the graphs and tables prepared by Thorsten in the presentation and pivot-tables of the XLS. - Additionally and for the deliverable the "scenario based" questionnairs in DOC format need to be analyzed and "highs" and "lows" need to be extracted for the chapters. - Stefano wanted everybody to analyze the bare-metal XLS and try to come up with "new interesting" things somebody sees in the day. This task needs to be worked on in parallel within the week of 14.10. - 18.10. - everybody to report relevant findings on the 22.10. Rough time plan: KW42 (14.-18.10): main content work, Testbed-team writing what we "see", judged by the numbers KW43 (21.-25.10): finalizing text & hand-over to WPL/WPA team - 22th of October: deadline for the content work - goal: on 23th October WPL/WPA should be able to start their work with the content analysis (you will have ~3 business days) KW44 (28.-30.10): finalizing the DOC deliverable and starting a review cycle - Please volunteer if you want to be a reviewer for this deliverable KW44 (31.10): planned submission to EC Please - if possible - directly update the wiki on https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/The_Validation_Analysis or the underlying pages. If unsure, just write the text in any other format and provide it ASAP to Thorsten so he can integrated it to the wiki. Find attached the updated presentation & the bare-metal data in XLS format. Assignments for writing the Analysis: - Cloud-chapter: John - Data: Clara - IoT: Salvatore - Overall FI-WARE: Stefano - Methodologie: Thorsten - Open chapters: o Apps o Security (ask Pascal) o Use Case chapters (all of them not assigned) Any questions or corrections, please let me know /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D1052b_WP10_v1_generated.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1372097 bytes Desc: D1052b_WP10_v1_generated.docx URL: From mev at tid.es Sat Oct 19 21:25:23 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Sat, 19 Oct 2013 19:25:23 +0000 Subject: [Fiware-wpl] Agile dynamic Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890D2D1D@EX10-MB2-MAD.hi.inet> Dear WP Leaders, Please, find linked the dashboard and review corresponding to this week: WP3 (Markus) https://forge.fi-ware.eu/docman/view.php/27/2930/FIWARE.backlog.apps.dashboard.20131019-1903.xlsx https://forge.fi-ware.eu/docman/view.php/27/2924/FIWARE.backlog.apps.review.20131019-1901.xlsx WP4 (Alex) https://forge.fi-ware.eu/docman/view.php/27/2931/FIWARE.backlog.cloud.dashboard.20131019-1903.xlsx https://forge.fi-ware.eu/docman/view.php/27/2925/FIWARE.backlog.cloud.review.20131019-1901.xlsx WP5 (Thierry) https://forge.fi-ware.eu/docman/view.php/27/2934/FIWARE.backlog.iot.dashboard.20131019-1904.xlsx https://forge.fi-ware.eu/docman/view.php/27/2928/FIWARE.backlog.iot.review.20131019-1902.xlsx WP6 (Sergio) https://forge.fi-ware.eu/docman/view.php/27/2932/FIWARE.backlog.data.dashboard.20131019-1903.xlsx https://forge.fi-ware.eu/docman/view.php/27/2926/FIWARE.backlog.data.review.20131019-1902.xlsx WP7 (Pier) https://forge.fi-ware.eu/docman/view.php/27/2933/FIWARE.backlog.i2nd.dashboard.20131019-1904.xlsx https://forge.fi-ware.eu/docman/view.php/27/2927/FIWARE.backlog.i2nd.review.20131019-1902.xlsx WP8 (Pascal) https://forge.fi-ware.eu/docman/view.php/27/2935/FIWARE.backlog.security.dashboard.20131019-1904.xlsx https://forge.fi-ware.eu/docman/view.php/27/2929/FIWARE.backlog.security.review.20131019-1903.xlsx I want to appreciate the effort done at I2nd - more than 120 records updated. I want to emphasize some chapters have still active enablers with nothing scheduled in their backlog - being at day 19th, it is not acceptable Apps (1), Cloud (3), IoT(6), Data(0), I2ND(0), Security(3) - I'd appreciate the corresponding WPLeaders to arrange bilateral meetings with the GEI Owners in order to fix it ASAP. I want to emphasize just a few enablers have some items burn down up to now. Therefore, this week there's need to remind GEI owners of closing finished items. Thanks all for cooperation! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Oct 21 09:54:07 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 21 Oct 2013 09:54:07 +0200 Subject: [Fiware-wpl] [Fiware-exploitation] FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 "Standardisation has become labeled as Exploitation?" In-Reply-To: <58967817BA9AEA4E92A38F89CE2EA932552730C2@DAPHNIS.office.hd> References: <58967817BA9AEA4E92A38F89CE2EA932552730C2@DAPHNIS.office.hd> Message-ID: <5264DD9F.50904@tid.es> Dear Lindsay, I am not sure I am understanding this correctly. Feel free speak your mind if I get it wrong. As you know, the reviewers have complained in previous reports that the reporting does not show a per partner/task granularity. We are just addressing this request. We spoke to Arian directly and committed ourselves to provide this breakdown. We have just created a structure that is common to all WPs and tasks; this applies to 11.4 as to any other tasks in the project. If a given partner has no standardization plans, he'll be individually showing it clearly instead of hiding in the crowd. I am aware that despite of a commendable personal effort on your side, the overall evaluation of the reviewers have been negative for the standardization tasks due to the generally insufficient inputs you have received(let us face it, while I disagree in other areas, my personal opinion is that the verdict is difficult to dispute here). As for your remark that standardisation is being labelled as exploitation, I am not sure if I get it right but I understand that you complain about a lax approach to naming that we colloquially adopt in the internal work, it should not be a big issue. We tend to refer to WP11 (officially "Exploitation and Standardisation") as "exploitation" the same as we refer to WP12 as "dissemination" (but the official name is "Communication, Collaboration and Dissemination"). There are more examples, we always say "Apps" but WP3 should be called "Application and Services Ecosystem and Delivery Framework", etc. Even if "Standardisation is not an Exploitation activity" , as you rightly point out, it is definitely a task and it follows the same pattern as any other tasks in the project. Maybe I do not get it and you refer to something else, I do not know! :) Each and every partner involved should do this work, I cannot agree more with you: you mustn't decide what their standardization plans are. Going to the DoW, "Task 11.4: Contribution to Standardisation" seems to involve these partners: TID, SAP, IBM-IL, THALES, TI, FT, DT, ALU-I, ALU-D, SIEMENS, INTEL, NEC (leader), DFKI, EPROS, iMinds Does this sound ok to you? As regards your fear that some partners may fail to provide inputs or very poor ones, it is a realistic risk, given the previous experience. In summary, my suggestion is that each one should be responsible for their own inputs. This means that if one fails to provide the inputs, you can add a "*** have not supplied their standardization plans". Which is the bare truth. And if the EC rejects part of their MM, so be it. Best regards, Miguel El 17/10/2013 22:58, Lindsay Frost escribi?: Dear Juan, dear all, I am surprised that Standardisation has become labeled as Exploitation. Do I understand right? The fact of the situation is that FIWARE is not "exploiting" standardization. Filling in the sheet below will not be easy for Partners, because (as you all know) there is no forward-planning for standardization, so there is no "main progress, main deviation, corrective action". The deliverables so far have all basically just reported what Partners did in SDOs. That is the factual situation. "Post hoc" activity reports. I am willing to help fill in the sheet below somehow, but I will need each and every partner (who as you know are not paid to do SDO work) to send me information basically like this: Our company XYZ is working mainly in WP n and m, where we consider the key standards where we can contribute to be a, b, c. Accordingly, we have for the last year been working on xxxxxx in order to zzzzzzz. The main result(s) so far have been 1111, 2222, 3333. /We are satisfied/We see a need to .../We have stopped ..../ (pick one) and will therefore in the next period or reporting do /nothing/something/... /(explain one). Do you (all) consider this a reasonable approach, with a likelihood of success? Or should I just write a paragraph of text explaining that "Standardisation is not an Exploitation activity" ? Thank you for your guidance, Lindsay SHEET TO BE FILLED IN, COPIED FROM THE WORD DOCUMENT SENT BY JUAN 1.1.1.1 Task 11.4: Contribution to Standardisation The objective of this task 11.4 is xxx. The breakdown of the contribution (please describe the main progress, main result, main deviation and main proposed corrective action) of each partner in this task 11.4 is: * 01-TID: xxx. * 02-SAP: xxx. * 03-IBM-IL: xxx. * 05-THALES: xxx. * 06-TI: xxx. * 07-FT: xxx. * 11-DT: xxx. * 16-ALU-I: xxx. * 17-ALU-D: xxx. * 18-SIEMENS: xxx. * 19-INTEL: xxx. * 20-NEC: xxx. * 29-DFKI: xxx. * 31-EPROS: xxx. * 32-IMINDS: xxx. From: Juan Bare?o Guerenabarrena [mailto:juan.bareno at atos.net] Sent: Donnerstag, 17. Oktober 2013 16:41 To: fiware-exploitation at lists.fi-ware.eu; fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: nuria.delama at atos.net; Lindsay Frost; javier.devicente at futuranetworks.com; mcp at tid.es; jdps at tid.es Subject: FW: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Dear Exploitation Colleagues 1. Progress report: request for contributions 2. Periodic Report M30 starts on May 2013 (M25) and ends on October 2013 (M30). 3. Each partner fulfill its participation in each Task a. 11.1 Market Analysis- nothing new since the last M24 Deliverable b. 11.2 Exploitation- The Individual Confidential Exploitation Plans after the review and the ones requested for M30 c. 11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe the CONCORD meetings d. 11.4 Standardization- Lindsay?? e. 11.5 Community Building- Javier?? 4. Deadline next Friday 25th October Thanks for your support Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: JAVIER DE PEDRO SANCHEZ [mailto:jdps at tid.es] Sent: martes, 15 de octubre de 2013 15:56 To: Juan Bare?o Guerenabarrena Cc: subsidies at tid.es Subject: RE: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Hola Juan Te remito la plantilla del WP11. Cada socio debe ser evaluado por a nivel de tarea. Por favor, conf?rmame que te ha llegado ?ste correo. Gracias mil. Salu2. Javier. De: subsidies-bounces at tid.es [mailto:subsidies-bounces at tid.es] En nombre de JAVIER DE PEDRO SANCHEZ Enviado el: martes, 15 de octubre de 2013 15:40 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: [Subsidies] FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: [cid:image001.png at 01CEBE9E.1EC99280] So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ _______________________________________________ Fiware-exploitation mailing list Fiware-exploitation at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-exploitation -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 339 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 4064 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 45089 bytes Desc: not available URL: From mcp at tid.es Mon Oct 21 10:29:04 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 21 Oct 2013 10:29:04 +0200 Subject: [Fiware-wpl] Minutes for today Message-ID: <5264E5D0.8020901@tid.es> Dear ll, Here it is. Work in progress :) https://docs.google.com/document/d/1keREFi6tQPy36tPSxm3TYHeD_K0it37PF_mvQiKw9Po/edit?pli=1# See you in a sec Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From Lindsay.Frost at neclab.eu Mon Oct 21 10:33:35 2013 From: Lindsay.Frost at neclab.eu (Lindsay Frost) Date: Mon, 21 Oct 2013 08:33:35 +0000 Subject: [Fiware-wpl] [Fiware-exploitation] FI-WARE: Periodic Report M30 (D.1.2.5) --> WP11 request to Partners for contact email addresses Message-ID: <58967817BA9AEA4E92A38F89CE2EA93255273DDC@DAPHNIS.office.hd> Dear Miquel, thank you very much for the clarifications! I have "got it" now :-) Dear Partners, i.e. TID, SAP, IBM-IL, THALES, TI, FT, DT, ALU-I, ALU-D, SIEMENS, INTEL, DFKI, EPROS, iMinds Would you please (a) tell me the person (+email) responsible to provide new standardization info for your organization, so I can communicate with them directly and quickly (b) send the information about your standardization work. The red text below may be a template, or you can suggest improvements. Partners which do not send text will have the default text "have not supplied standardization plans" Draft Template for inputs: Our company XYZ is working mainly in WP n and m, where we consider the key standards where we can contribute to be a, b, c. Accordingly, we have for the last year been working on xxxxxx in order to zzzzzzz. We have been collaborating with the FIWARE partner ZZZ //if applicable//. The main result(s) so far have been 1111, 2222, 3333. Some main contributions and meetings attended are shown in wiki //please update//. //We are satisfied/We see a need to .../We have stopped ..../ //pick one// and will therefore in the next period of reporting do /nothing/something/... ///explain one//. Thank you very much Lindsay ________________________________________ Dr. Lindsay Frost, Chief Standardization Eng. frost at neclab.eu Mobile +49.163.275.1734 NEC Laboratories Europe, Kurf?rsten-Anlage 36, D-69115 Heidelberg, Germany. Reg. Headoffice: NEC Europe Ltd, VAT DE161569151 Athene, Odyssey Business Park, West End Road, London HA4 6QE, Reg. in England 2832014 From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Montag, 21. Oktober 2013 09:54 To: Lindsay Frost; Juan Bare?o Guerenabarrena; fiware-exploitation at lists.fi-ware.eu; fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-exploitation] FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 "Standardisation has become labeled as Exploitation?" Dear Lindsay, I am not sure I am understanding this correctly. Feel free speak your mind if I get it wrong. As you know, the reviewers have complained in previous reports that the reporting does not show a per partner/task granularity. We are just addressing this request. We spoke to Arian directly and committed ourselves to provide this breakdown. We have just created a structure that is common to all WPs and tasks; this applies to 11.4 as to any other tasks in the project. If a given partner has no standardization plans, he'll be individually showing it clearly instead of hiding in the crowd. I am aware that despite of a commendable personal effort on your side, the overall evaluation of the reviewers have been negative for the standardization tasks due to the generally insufficient inputs you have received(let us face it, while I disagree in other areas, my personal opinion is that the verdict is difficult to dispute here). As for your remark that standardisation is being labelled as exploitation, I am not sure if I get it right but I understand that you complain about a lax approach to naming that we colloquially adopt in the internal work, it should not be a big issue. We tend to refer to WP11 (officially "Exploitation and Standardisation") as "exploitation" the same as we refer to WP12 as "dissemination" (but the official name is "Communication, Collaboration and Dissemination"). There are more examples, we always say "Apps" but WP3 should be called "Application and Services Ecosystem and Delivery Framework", etc. Even if "Standardisation is not an Exploitation activity" , as you rightly point out, it is definitely a task and it follows the same pattern as any other tasks in the project. Maybe I do not get it and you refer to something else, I do not know! :) Each and every partner involved should do this work, I cannot agree more with you: you mustn't decide what their standardization plans are. Going to the DoW, "Task 11.4: Contribution to Standardisation" seems to involve these partners: TID, SAP, IBM-IL, THALES, TI, FT, DT, ALU-I, ALU-D, SIEMENS, INTEL, NEC (leader), DFKI, EPROS, iMinds Does this sound ok to you? As regards your fear that some partners may fail to provide inputs or very poor ones, it is a realistic risk, given the previous experience. In summary, my suggestion is that each one should be responsible for their own inputs. This means that if one fails to provide the inputs, you can add a "*** have not supplied their standardization plans". Which is the bare truth. And if the EC rejects part of their MM, so be it. Best regards, Miguel El 17/10/2013 22:58, Lindsay Frost escribi?: Dear Juan, dear all, I am surprised that Standardisation has become labeled as Exploitation. Do I understand right? The fact of the situation is that FIWARE is not "exploiting" standardization. Filling in the sheet below will not be easy for Partners, because (as you all know) there is no forward-planning for standardization, so there is no "main progress, main deviation, corrective action". The deliverables so far have all basically just reported what Partners did in SDOs. That is the factual situation. "Post hoc" activity reports. I am willing to help fill in the sheet below somehow, but I will need each and every partner (who as you know are not paid to do SDO work) to send me information basically like this: Our company XYZ is working mainly in WP n and m, where we consider the key standards where we can contribute to be a, b, c. Accordingly, we have for the last year been working on xxxxxx in order to zzzzzzz. The main result(s) so far have been 1111, 2222, 3333. /We are satisfied/We see a need to .../We have stopped ..../ (pick one) and will therefore in the next period or reporting do /nothing/something/... /(explain one). Do you (all) consider this a reasonable approach, with a likelihood of success? Or should I just write a paragraph of text explaining that "Standardisation is not an Exploitation activity" ? Thank you for your guidance, Lindsay SHEET TO BE FILLED IN, COPIED FROM THE WORD DOCUMENT SENT BY JUAN 1.1.1.1 Task 11.4: Contribution to Standardisation The objective of this task 11.4 is xxx. The breakdown of the contribution (please describe the main progress, main result, main deviation and main proposed corrective action) of each partner in this task 11.4 is: * 01-TID: xxx. * 02-SAP: xxx. * 03-IBM-IL: xxx. * 05-THALES: xxx. * 06-TI: xxx. * 07-FT: xxx. * 11-DT: xxx. * 16-ALU-I: xxx. * 17-ALU-D: xxx. * 18-SIEMENS: xxx. * 19-INTEL: xxx. * 20-NEC: xxx. * 29-DFKI: xxx. * 31-EPROS: xxx. * 32-IMINDS: xxx. From: Juan Bare?o Guerenabarrena [mailto:juan.bareno at atos.net] Sent: Donnerstag, 17. Oktober 2013 16:41 To: fiware-exploitation at lists.fi-ware.eu; fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: nuria.delama at atos.net; Lindsay Frost; javier.devicente at futuranetworks.com; mcp at tid.es; jdps at tid.es Subject: FW: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Dear Exploitation Colleagues 1. Progress report: request for contributions 2. Periodic Report M30 starts on May 2013 (M25) and ends on October 2013 (M30). 3. Each partner fulfill its participation in each Task a. 11.1 Market Analysis- nothing new since the last M24 Deliverable b. 11.2 Exploitation- The Individual Confidential Exploitation Plans after the review and the ones requested for M30 c. 11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe the CONCORD meetings d. 11.4 Standardization- Lindsay?? e. 11.5 Community Building- Javier?? 4. Deadline next Friday 25th October Thanks for your support Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: JAVIER DE PEDRO SANCHEZ [mailto:jdps at tid.es] Sent: martes, 15 de octubre de 2013 15:56 To: Juan Bare?o Guerenabarrena Cc: subsidies at tid.es Subject: RE: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Hola Juan Te remito la plantilla del WP11. Cada socio debe ser evaluado por a nivel de tarea. Por favor, conf?rmame que te ha llegado ?ste correo. Gracias mil. Salu2. Javier. De: subsidies-bounces at tid.es [mailto:subsidies-bounces at tid.es] En nombre de JAVIER DE PEDRO SANCHEZ Enviado el: martes, 15 de octubre de 2013 15:40 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: [Subsidies] FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: [cid:image001.png at 01CEBE9E.1EC99280] So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ _______________________________________________ Fiware-exploitation mailing list Fiware-exploitation at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-exploitation -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 45089 bytes Desc: image003.jpg URL: From jhierro at tid.es Wed Oct 23 07:36:09 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 23 Oct 2013 07:36:09 +0200 Subject: [Fiware-wpl] IMPORTANT: Extension of the project duration Message-ID: <52676049.8020105@tid.es> Hi all, As we have discussed a couple of times, the EC has suggested an extension of the FI-WARE project duration for at least 4 additional months. This was actually a recommendation given in the last review report. This was a topic that I have encouraged you to discuss with the teams in your respective chapters. During our meetings, it was also agreed that extension of the project would mean a request to move the dates of those deliverables linked to release of software and accompanying documentation so that they change to be month 36 instead of 33. Those deliverables linked to deployment of software on the FI-PPP Testbed and FI-LAB which were planned for month 36 would also be delayed until month 40. We didn't discuss this but I guess we would agree that some of the final reports to be produced should also be delayed from month 36 until month 40. So far, the only feedback I have got is that partners would be ok for the proposed extension, provided the mentioned changes in deliverable dates are incorporated. With all these considerations in mind, I have produced the attached updated version of the Deliverable List. Changes are highlighted so that you can easily track them. Of course, your feedback is welcome. Unless I hear about any objection from your side before this Friday EOB, I will submit an official response to the EC announcing our agreement to extend the project duration another 4 months (i.e., until end of August 2014), provided the changes we propose in the deliverable dates are accepted. I will use the attached table as basis although I'm happy to incorporate some additional changes you may consider necessary. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE-DoW-Amendment5 deliverable list (version_date-13-07-17) DRAFT.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 90967 bytes Desc: not available URL: From mcp at tid.es Wed Oct 23 14:02:33 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 23 Oct 2013 14:02:33 +0200 Subject: [Fiware-wpl] Latest internal reviews of "sw related" deliverables resent Message-ID: <5267BAD9.3010905@tid.es> Dear all, As agreed on Monday, I just resent in private to each WPL/WPA the latest excel files with our reviews (Ferm?n's and mine). I refer to WP3-WP8 (it does not apply to the others) Please do not forget that Mauro's reviews (engineering) also apply and that must be addressed as well. We will shortly start adding workitems to your internal per chapter backlogs with the pending tasks, to follow up more closely. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From torsten.leidig at sap.com Wed Oct 23 14:23:11 2013 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 23 Oct 2013 12:23:11 +0000 Subject: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration Message-ID: <703F4EB81B2AD0428360BFE55A82DFBC5F2D7E5B@DEWDFEMB11B.global.corp.sap> Dear Juanjo, This is to inform you that SAP objects to the suggested extension of the FI-WARE project for a number of reasons: * We expect to finalize all our WP deliverables until end of April. * We also expect to deliver all contributions to general deliverables. * SAP internal resource, planning, and contractual constraints will not allow us to do substantial work after the original project end. Therefore an extension is counter productive. * We are seriously concerned that an extension will further delay the project. We don't understand why deliverables cannot be finalized and why. Just moving the deadlines is not enough to do a proper re-planning. We cannot estimate, which workload is imposed on us during this extension period. Please also be aware that 2 month of the extension fall into summer period, where usually not much happens. * The EC did not express a clear explanation, why they suggest an extension. The comments in the review report are very vague. We also don't understand why so many deliverables have to be moved 4 months. Is this really necessary? The approach should be to focus and get most of the deliverables ready at the original project end (We still have 6 month to work on it!) and leave only a very small number of deliverables for a possible extension. Also not all WP and partners might be necessary during this extension. Best regards, Torsten Leidig Dr. Torsten Leidig Research Expert Human Computer Interaction TIP PA&TS HCI Research SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7-52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, L?o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Oct 23 16:35:04 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 23 Oct 2013 16:35:04 +0200 Subject: [Fiware-wpl] New member on your projects Message-ID: <5267DE98.5030108@tid.es> Dear all, You will notice that I have added Santiago (user smg ) to the projects WP3-WP8 + WP13 on the forge. This stems from the fact that Juanjo is telling us to add workitems to your backlog directly and he will occasionally help us in this task. Incidentally, I see pending user approvals in cloud and security... you'll see what to do with them. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Thu Oct 24 09:25:48 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 24 Oct 2013 07:25:48 +0000 Subject: [Fiware-wpl] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486060DDF@DEWDFEMB11A.global.corp.sap> Dear WPL & WPA colleagues (apps, cloud, data, iot, security), as planned below I would like to encourage and ask kindly for your contributions to the validation deliverable, which for your chapter the Testbed Team prepared as attached & in the testbed wiki. You will find the task for "your" chapter described in the doc - the section you have to fill is "Comments by WP leadership" for your chapter and should roughly cover answers to the questions, which I as well printed at the bottom of this email. These questions might help you find relevant and "interesting" things, the Reviews would like to know in relation to our "answer" to the validation of the use cases in phase 1. Please either directly change the DOC-file with "tracked"-changes - or contribute to the wiki where all pages from this deliverable are linked here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page#Structure_of_this_Document Please finish this task until Monday, 28.10. EOB the latest. If you have any questions, please don't hesitate to ask! Thanks a lot and best regards /Thorsten Questions to be answered by WPL/WPA * What went good, what went bad during this validation? * What was the recent actions implemented which address potential challenges identified during the validation? * Which challenges did you mainly identify, coming out of this validation? * What strength can you find for your chapter and how to further build upon this strength? * What measures did you take to mitigate the situation? * Overall acceptance over all validated GE for your chapter? (find answer Q.GE.11) * How deep have they been validated for your chapter? (find answer QGE.13) * Browse through the "scenario-based answers" (doc-files) and extract some relevant quotes good ones and bad ones, touching on your chapter GEs. - the doc files are linked here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Overview_FI-WARE_validation#Validation_of_non-functional_requirements * What would you do differently in the next validation round? * What would you find interesting from the use cases to better improve the validation? De : fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] De la part de Sandfuchs, Thorsten Envoy? : lundi 14 octobre 2013 10:25 ? : fiware-testbed at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-testbed] Minutes and action points on validation deliverable submission (10.5.2b) Dear colleagues, on Friday there was a testbed-internal session which discussed how to submit D.10.5.2b (the resubmission of the validation deliverable). We have a very tight schedule to submit this deliverable with all contributions in time. For this minutes I'm taking WPL/WPA on the CC list in order to let everybody know the status. Thorsten presented the approach and explained along the lines of the presentation what content should needs to be produced. - Mainly the testbed-team will in a neutral way write what we "see", judged by the numbers - things like: "SMARTAGRIFOOD rated the integration badly in the case of the XXX chapter...." We could try to come up with first assumptions on why these ratings did take place and dig deeper - but overall WPL/WPA need to do the _content_ driven analysis. "The reason for this was ..." or "We will take this serious and already implemented the following actions ..." Background are the graphs and tables prepared by Thorsten in the presentation and pivot-tables of the XLS. - Additionally and for the deliverable the "scenario based" questionnairs in DOC format need to be analyzed and "highs" and "lows" need to be extracted for the chapters. - Stefano wanted everybody to analyze the bare-metal XLS and try to come up with "new interesting" things somebody sees in the day. This task needs to be worked on in parallel within the week of 14.10. - 18.10. - everybody to report relevant findings on the 22.10. Rough time plan: KW42 (14.-18.10): main content work, Testbed-team writing what we "see", judged by the numbers KW43 (21.-25.10): finalizing text & hand-over to WPL/WPA team - 22th of October: deadline for the content work - goal: on 23th October WPL/WPA should be able to start their work with the content analysis (you will have ~3 business days) KW44 (28.-30.10): finalizing the DOC deliverable and starting a review cycle - Please volunteer if you want to be a reviewer for this deliverable KW44 (31.10): planned submission to EC Please - if possible - directly update the wiki : https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page#Structure_of_this_Document or the underlying pages. If unsure, just write the text in any other format and provide it ASAP to Thorsten so he can integrated it to the wiki. Find attached the updated presentation & the bare-metal data in XLS format. Assignments for writing the Analysis: - Cloud-chapter: John - Data: Clara - IoT: Salvatore - Overall FI-WARE: Stefano - Methodologie: Thorsten - Open chapters: o Apps o Security (ask Pascal) o Use Case chapters (all of them not assigned) Any questions or corrections, please let me know /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D1052b_WP10_v2_generated.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1200520 bytes Desc: D1052b_WP10_v2_generated.docx URL: From jhierro at tid.es Thu Oct 24 11:09:12 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 24 Oct 2013 11:09:12 +0200 Subject: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration In-Reply-To: <703F4EB81B2AD0428360BFE55A82DFBC5F2D7E5B@DEWDFEMB11B.global.corp.sap> References: <703F4EB81B2AD0428360BFE55A82DFBC5F2D7E5B@DEWDFEMB11B.global.corp.sap> Message-ID: <5268E3B8.5060601@tid.es> Dear Torsten, I believe that nothing prevents that a given partner, or even a whole chapter, ends its work and submit their deliverables as defined in the original DoW. That would mean submitting in advance, which would not be that much an issue ... In other words, I don't have an issue if SAP closes its activities and deliverables following the original plan, while other chapter/partners keep working and deliver after closing release 3.3, planned by end of April (check [1]) ... would that work with you ? On the other hand ... Is this the sole position of SAP in WP3, or extension is an issue also for the rest of partners in the WP ? ... and BTW, for many of the deliverables that have to do with software release, specifications, software documentation (i.e., the more heavy ones) delivery dates are month 33, which means end of January 2014 ... so there are no 6 months from now but really 3 months ! Best regards, -- Juanjo [1] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates On 23/10/13 14:23, Leidig, Torsten wrote: Dear Juanjo, This is to inform you that SAP objects to the suggested extension of the FI-WARE project for a number of reasons: * We expect to finalize all our WP deliverables until end of April. * We also expect to deliver all contributions to general deliverables. * SAP internal resource, planning, and contractual constraints will not allow us to do substantial work after the original project end. Therefore an extension is counter productive. * We are seriously concerned that an extension will further delay the project. We don't understand why deliverables cannot be finalized and why. Just moving the deadlines is not enough to do a proper re-planning. We cannot estimate, which workload is imposed on us during this extension period. Please also be aware that 2 month of the extension fall into summer period, where usually not much happens. * The EC did not express a clear explanation, why they suggest an extension. The comments in the review report are very vague. We also don't understand why so many deliverables have to be moved 4 months. Is this really necessary? The approach should be to focus and get most of the deliverables ready at the original project end (We still have 6 month to work on it!) and leave only a very small number of deliverables for a possible extension. Also not all WP and partners might be necessary during this extension. Best regards, Torsten Leidig Dr. Torsten Leidig Research Expert Human Computer Interaction TIP PA&TS HCI Research SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7-52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, L?o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Thu Oct 24 11:32:32 2013 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Thu, 24 Oct 2013 09:32:32 +0000 Subject: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration In-Reply-To: <5268E3B8.5060601@tid.es> References: <703F4EB81B2AD0428360BFE55A82DFBC5F2D7E5B@DEWDFEMB11B.global.corp.sap>, <5268E3B8.5060601@tid.es> Message-ID: <703F4EB81B2AD0428360BFE55A82DFBC5F2D8207@DEWDFEMB11B.global.corp.sap> Dear Juanjo, We still don't understand why the extension is necessary esp. what's the intention of the EC/Reviewers, what do they expect to improve during the extension time. Your proposal to let SAP close its activities and deliverables following the original plan does not really work out well. There are many dependencies we have to sort out to let us work independently. Also we would properly not longer serve as a WPL/WPA for WP3. That's why we insist in a more detailed plan then just moving deliverables a few months. Regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen ________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: Thursday, October 24, 2013 11:09 AM To: Leidig, Torsten Cc: 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu'; Nochta, Zoltan; Theilmann, Wolfgang Subject: Re: [Fiware-wpa] IMPORTANT: Extension of the project duration Dear Torsten, I believe that nothing prevents that a given partner, or even a whole chapter, ends its work and submit their deliverables as defined in the original DoW. That would mean submitting in advance, which would not be that much an issue ... In other words, I don't have an issue if SAP closes its activities and deliverables following the original plan, while other chapter/partners keep working and deliver after closing release 3.3, planned by end of April (check [1]) ... would that work with you ? On the other hand ... Is this the sole position of SAP in WP3, or extension is an issue also for the rest of partners in the WP ? ... and BTW, for many of the deliverables that have to do with software release, specifications, software documentation (i.e., the more heavy ones) delivery dates are month 33, which means end of January 2014 ... so there are no 6 months from now but really 3 months ! Best regards, -- Juanjo [1] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates On 23/10/13 14:23, Leidig, Torsten wrote: Dear Juanjo, This is to inform you that SAP objects to the suggested extension of the FI-WARE project for a number of reasons: * We expect to finalize all our WP deliverables until end of April. * We also expect to deliver all contributions to general deliverables. * SAP internal resource, planning, and contractual constraints will not allow us to do substantial work after the original project end. Therefore an extension is counter productive. * We are seriously concerned that an extension will further delay the project. We don't understand why deliverables cannot be finalized and why. Just moving the deadlines is not enough to do a proper re-planning. We cannot estimate, which workload is imposed on us during this extension period. Please also be aware that 2 month of the extension fall into summer period, where usually not much happens. * The EC did not express a clear explanation, why they suggest an extension. The comments in the review report are very vague. We also don't understand why so many deliverables have to be moved 4 months. Is this really necessary? The approach should be to focus and get most of the deliverables ready at the original project end (We still have 6 month to work on it!) and leave only a very small number of deliverables for a possible extension. Also not all WP and partners might be necessary during this extension. Best regards, Torsten Leidig Dr. Torsten Leidig Research Expert Human Computer Interaction TIP PA&TS HCI Research SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7-52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, L?o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Oct 24 16:46:56 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 24 Oct 2013 16:46:56 +0200 Subject: [Fiware-wpl] R: [Fiware-pcc] IMPORTANT: Extension of the project duration In-Reply-To: <52676049.8020105@tid.es> References: <52676049.8020105@tid.es> Message-ID: Dear Juanjo, here is the feedback I got from (nearly all) the partners in I2ND chapter in our periodic call this morning, concerning the proposal to extend the project duration and modify the date for the deliverables you mentioned: - Fraunhofer: tend to not agree on extending, however they would accept the decision of majority and have no objections on any decision - ALU-D (ALU-I?): no objections, to be clarified what really should be the outcome of the additional months and what would be the related work load expected - DT: there might be no need for extensions for their activity in nearly all chapters, also in WP7 it is expected that work is completed in time, so no real need for extending the project, however the decision is up to the consortium - Technicolor: no real need, however it would be accepted what decided - Intel: considered this in WP4 as well. Need to check back with management (maybe in a couple of days they have the feedback) - NSN-H: Need to check back with management Not present Orange (but this is a topic managed by Thierry) and UNIROMA1, I'll check with the latter what's their position asap, as well as with ALU-I which is probably in line with ALU-D but it needs a verification. One additional note raised by some of the partners: they questioned that information was provided through the WPs only, whilst the global list, or management people of all partners, should have been informed properly... BR Pier Da: fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 23 ottobre 2013 07:36 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Oggetto: [Fiware-pcc] IMPORTANT: Extension of the project duration Hi all, As we have discussed a couple of times, the EC has suggested an extension of the FI-WARE project duration for at least 4 additional months. This was actually a recommendation given in the last review report. This was a topic that I have encouraged you to discuss with the teams in your respective chapters. During our meetings, it was also agreed that extension of the project would mean a request to move the dates of those deliverables linked to release of software and accompanying documentation so that they change to be month 36 instead of 33. Those deliverables linked to deployment of software on the FI-PPP Testbed and FI-LAB which were planned for month 36 would also be delayed until month 40. We didn't discuss this but I guess we would agree that some of the final reports to be produced should also be delayed from month 36 until month 40. So far, the only feedback I have got is that partners would be ok for the proposed extension, provided the mentioned changes in deliverable dates are incorporated. With all these considerations in mind, I have produced the attached updated version of the Deliverable List. Changes are highlighted so that you can easily track them. Of course, your feedback is welcome. Unless I hear about any objection from your side before this Friday EOB, I will submit an official response to the EC announcing our agreement to extend the project duration another 4 months (i.e., until end of August 2014), provided the changes we propose in the deliverable dates are accepted. I will use the attached table as basis although I'm happy to incorporate some additional changes you may consider necessary. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From mcp at tid.es Fri Oct 25 12:09:04 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 25 Oct 2013 12:09:04 +0200 Subject: [Fiware-wpl] Organization of Release 3 Message-ID: <526A4340.6090703@tid.es> Dear WPLs/WPAs, At the end of this message there is a draft version of the e-mail we intend to send to the general list early on Monday. This time we did not modify the procedure as changing things seems to be too confusing for people. If you go to the links (already there), we are going to avoid the "_R2" in the page names so you will not need to change the names in the porting to the public wiki. Best regards, Miguel ===================================== Dear all, We have the links to edit the deliverables ready on the private wiki now, with the usual rules. * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR3 Be aware that: * We have made an effort to keep the same old rules from R2 for the sake of simplicity * This message refers to the Unit Testing Plan, User & Prog. Manual and Install & Admin guides * This message refers to WP3, WP4, WP5, WP6, WP7, WP8 and WP13 * As stated in the wiki pages with the placeholders, the WPL have to fill in the list of GEs/GEis per deliverable. Once they add the links, you can start your work. Coordinate internally in each WP. * Editing the deliverables on the public wiki is not allowed - we will strictly enforce it this time. The editing of the manuals should happen on the private wiki * Yes, we know that there are deliverables from R2 not yet accepted. They will undergo reviews later but we cannot delay R3 anymore. * There is a single compulsory delivery at the end of R3. However, if part of the GE owners wishes to deliver at the end of a minor release, they can. This would imply delivering internally on the private wiki first, making sure that it is a full and consistently synchronised delivery (software + manual fully updated for the minor release). Then they would undergo reviews and get the approval for final publication. As for the timing, there is an ongoing discussion whether we will extend the project. So far SAP has vetoed an extension so for the moment we will have to plan with the current DoW. This means that the final delivery is M33 (Jan/2014) which means that we should start the reviews before the end of the year. The deadline is 15/December, each WPL will organize the internal schedule in each WP . Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Fri Oct 25 14:27:24 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Fri, 25 Oct 2013 14:27:24 +0200 Subject: [Fiware-wpl] IMPORTANT: Extension of the project duration In-Reply-To: <52676049.8020105@tid.es> References: <52676049.8020105@tid.es> Message-ID: <526A63AC.3010803@eng.it> Dear Juanjo, I report you here and in the attached document (in track changes) the position of the Tools Chapter with regards the deliverable dates. Deliverables to be moved to *M36* D9.1.d FI-CoDE Basic Framework D9.2.c FI-CoDE Handbook Deliverable to stay at *M33* D9.3.c API IDE Support D9.4.c Application Testing and Deployment Support Tools kind regards, Davide On 23/10/2013 07:36, Juanjo Hierro wrote: > Hi all, > > As we have discussed a couple of times, the EC has suggested an > extension of the FI-WARE project duration for at least 4 additional > months. This was actually a recommendation given in the last review > report. > > This was a topic that I have encouraged you to discuss with the > teams in your respective chapters. > > During our meetings, it was also agreed that extension of the > project would mean a request to move the dates of those deliverables > linked to release of software and accompanying documentation so that > they change to be month 36 instead of 33. Those deliverables linked > to deployment of software on the FI-PPP Testbed and FI-LAB which were > planned for month 36 would also be delayed until month 40. We didn't > discuss this but I guess we would agree that some of the final reports > to be produced should also be delayed from month 36 until month 40. > > So far, the only feedback I have got is that partners would be ok > for the proposed extension, provided the mentioned changes in > deliverable dates are incorporated. > > With all these considerations in mind, I have produced the attached > updated version of the Deliverable List. Changes are highlighted so > that you can easily track them. Of course, your feedback is welcome. > > Unless I hear about any objection from your side before this Friday > EOB, I will submit an official response to the EC announcing our > agreement to extend the project duration another 4 months (i.e., until > end of August 2014), provided the changes we propose in the > deliverable dates are accepted. I will use the attached table as > basis although I'm happy to incorporate some additional changes you > may consider necessary. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > FI-PPP Architecture Board chairman > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE-DoW-Amendment5 deliverable list (version_date-13-07-17) DRAFT DDC.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 15194 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Sat Oct 26 11:45:14 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Sat, 26 Oct 2013 11:45:14 +0200 Subject: [Fiware-wpl] FI-WARE Progress Report - THALES input (to your WP Progress Report) Message-ID: <26067_1382780724_526B8F33_26067_1201_1_f1298ad4-d476-4406-b113-e89dac801e18@THSONEA01HUB01P.one.grp> Dear WP Lead colleagues, Please find attached to this email the Thales wide input - as per today - to Progress Report M25-M30. This in order for you to use and take out of it what needs to go for Thales at the level of the Progress Report of the WP you lead. FYI I would be on vacation next week but Daniel (in cc) would replace me. As for the missing contrib. at WP4 and WP3 level I count on Lionel/Mario and Pierre as participants to these WPs to send them to WP4 Lead (Alex) and WP3 Lead (Markus) asap and cc me/Daniel/Corinne. Best Regards, Pascal PS: I put Thales colleagues involved in your WP in cc of that email for their information also records.s -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - M25-M30 Rreporting per WP THALES 2013-10-24.doc Type: application/msword Size: 270848 bytes Desc: FI-WARE - M25-M30 Rreporting per WP THALES 2013-10-24.doc URL: From jhierro at tid.es Mon Oct 28 00:56:53 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Sun, 27 Oct 2013 23:56:53 +0000 Subject: [Fiware-wpl] Canceled: Joint WPLs/WPAs follow-up confcall (Part I) Message-ID: <936DECD07EB54B4BAA44E7B823EC89418537EB32@EX10-MB2-MAD.hi.inet> Joint WPLs/WPAs follow-up confcalls are splitted into two parts. This is the first one and we will always stick to the end time. Topics not addressed in this slot will be treated in the slot of the afternoon. The slot in the afternoon will be used to also address Technical-Architecture issues. We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4131 bytes Desc: not available URL: From jhierro at tid.es Mon Oct 28 00:56:57 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Sun, 27 Oct 2013 23:56:57 +0000 Subject: [Fiware-wpl] Canceled: Joint WPLs/WPAs follow-up confcall (Part II) Message-ID: <936DECD07EB54B4BAA44E7B823EC89418537EB9A@EX10-MB2-MAD.hi.inet> Joint WPLs/WPAs follow-up confcalls are split into two parts. This is the second one and we will always stick to the end time. Topics not addressed in the first slot will be treated in this slot of the afternoon. This slot will also be used to also address Technical-Architecture issues. We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4016 bytes Desc: not available URL: From jhierro at tid.es Mon Oct 28 02:03:02 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 28 Oct 2013 02:03:02 +0100 Subject: [Fiware-wpl] Weekly follow-up confcall cancelled Message-ID: <526DB7C6.7080206@tid.es> Dear all, Miguel is on holidays this week and I won't be able to attend myself the planned confcall, so I go for cancelling it. I understand that the several APs are clear and that we may discuss any issue over the email. I call your attention to the email sent by Miguel last Friday regarding the process to be followed for preparing the delivery of software and accompanying documentation of Release 3 (R3) as well as the instructions about requeriments to be met to keep consistency between what is available in the public wiki and what it has been available in the different environments (FI-PPP and FI-LAB) to be also kept aligned with what is advertised in the catalogue. I will send the email drafted by Miguel to the whole FI-WARE partners this afternoon so if you have any comment, please react quickly. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Mon Oct 28 14:31:44 2013 From: markus.heller at sap.com (Heller, Markus) Date: Mon, 28 Oct 2013 13:31:44 +0000 Subject: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration --> request for update Message-ID: <393554EDCF801348BC53C7813C6CB73B1A6821C5@DEWDFEMB14A.global.corp.sap> Dear Juanjo, Since we did not have the WPL/WPA call today, I would like to address the FI-WARE project extension topic here. If I am right, you wrote in one of your mails on this that you have intended to send a consortium statement message to EC at end of the last week. Can I please ask you for an update on the discussed FI-WARE Extension topic and how we plan to drive this forward? Additionally, I have the following questions on this topic: 1. Do we have an answer from EC /reviewers for the question who requested it (EC, reviewers, both) and what they think should be done/improved in the extension period? If I recall tight, there was an action item either in one of the PCC call / WPL&WPA call on this. 2. As I have understood in my other mails, some other partners also sent a "rather not" message to you like we did (but most tied it to a statement like "if all others go for it we would maybe join in"). Do you have an current overview who prefers to either go for an extension or to not go for an extension - e.g. on the WPL/WPA mailing list? 3. Time Frame: Do we (still) talk about a possible extension of 4 months - or has something changed in the meantime w.r.t. extension time frame? 4. Budget for extension: Would the extension be somewhat budget-neutral or would the extension come with any additional funding? Of course, I guess the extension would be budget-neutral, right? This question maybe has been already addressed during my vacation... Torsten shared our current SAP opinion on a possible extension below and I would also be interested in your opinion on his reply to you given below, for example, how such a mixed approach (some partners stay vs. some partners leave) can be organized with a detail plan to make sure the split-up really works out well to avoid last mile damage to the project due to failing handovers or necessary result reductions etc... If you agree, we can try to go on with e-mail during the week to bring the topic forward since there is no other coordination call currently scheduled this week if I see right. Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: Donnerstag, 24. Oktober 2013 11:33 To: Juanjo Hierro Cc: Theilmann, Wolfgang; 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu'; Nochta, Zoltan Subject: Re: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration Dear Juanjo, We still don't understand why the extension is necessary esp. what's the intention of the EC/Reviewers, what do they expect to improve during the extension time. Your proposal to let SAP close its activities and deliverables following the original plan does not really work out well. There are many dependencies we have to sort out to let us work independently. Also we would properly not longer serve as a WPL/WPA for WP3. That's why we insist in a more detailed plan then just moving deliverables a few months. Regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen ________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: Thursday, October 24, 2013 11:09 AM To: Leidig, Torsten Cc: 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu'; Nochta, Zoltan; Theilmann, Wolfgang Subject: Re: [Fiware-wpa] IMPORTANT: Extension of the project duration Dear Torsten, I believe that nothing prevents that a given partner, or even a whole chapter, ends its work and submit their deliverables as defined in the original DoW. That would mean submitting in advance, which would not be that much an issue ... In other words, I don't have an issue if SAP closes its activities and deliverables following the original plan, while other chapter/partners keep working and deliver after closing release 3.3, planned by end of April (check [1]) ... would that work with you ? On the other hand ... Is this the sole position of SAP in WP3, or extension is an issue also for the rest of partners in the WP ? ... and BTW, for many of the deliverables that have to do with software release, specifications, software documentation (i.e., the more heavy ones) delivery dates are month 33, which means end of January 2014 ... so there are no 6 months from now but really 3 months ! Best regards, -- Juanjo [1] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates On 23/10/13 14:23, Leidig, Torsten wrote: Dear Juanjo, This is to inform you that SAP objects to the suggested extension of the FI-WARE project for a number of reasons: * We expect to finalize all our WP deliverables until end of April. * We also expect to deliver all contributions to general deliverables. * SAP internal resource, planning, and contractual constraints will not allow us to do substantial work after the original project end. Therefore an extension is counter productive. * We are seriously concerned that an extension will further delay the project. We don't understand why deliverables cannot be finalized and why. Just moving the deadlines is not enough to do a proper re-planning. We cannot estimate, which workload is imposed on us during this extension period. Please also be aware that 2 month of the extension fall into summer period, where usually not much happens. * The EC did not express a clear explanation, why they suggest an extension. The comments in the review report are very vague. We also don't understand why so many deliverables have to be moved 4 months. Is this really necessary? The approach should be to focus and get most of the deliverables ready at the original project end (We still have 6 month to work on it!) and leave only a very small number of deliverables for a possible extension. Also not all WP and partners might be necessary during this extension. Best regards, Torsten Leidig Dr. Torsten Leidig Research Expert Human Computer Interaction TIP PA&TS HCI Research SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7-52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, L?o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Mon Oct 28 17:48:57 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 28 Oct 2013 16:48:57 +0000 Subject: [Fiware-wpl] Agile Dynamic - End of sprint 3.2.1 -> Request for action Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E5457@EX10-MB2-MAD.hi.inet> Dear Partners, Please, find below the dashboard and review files of the different chapters. When having a look at the chapters' dashboards, it can be said Cloud chapter has the best diagram, although a sudden valley or cliff should appear from 28 onwards. [cid:image001.png at 01CED402.C2F767A0] During the next four days, it's important that you update the status of your backlog items. I'm taking as an example a good backlog, that from Lorenzo, to remind of the directions. [cid:image002.png at 01CED403.431E9070] Lorenzo has already closed items as he was finishing them. Good!! - Congratulations. Therefore, the actions are: 1. Check whether items in 'Under verification' (5047) and 'Under execution' (5053, 5051) can be closed. In this case the Feature(5050) doesn't need any change as it keeps going during the release 2. Not finished items and Items in status scheduled (5070, 5071, 5072, 4715) probably need to be moved to Sprint.3.2.2 Updating both the status and the timeframes shouldn't take more than 5 minutes. I see Lorenzo has introduced work items for the Catalogue, and the sprint planning, and other tasks in the testbed and Fi-LAB, this is the way to do it. So Lorenzo, let me congratulate you again!!! I hope this way to visualize the direction, which is more concrete, is more helpful. If you needed any help for your particular GE, please, let me know. If anything, please, don't hesitate to let me know. Kind regards, Manuel -------------------------------- Files below: Dashboards: WP3-Apps [1]; WP4-Cloud [2]; WP5-IoT[3]; WP6-Data[4]; WP7-I2nd[5]; WP8-Sec[6] [1]: https://forge.fi-ware.eu/docman/view.php/27/2949/FIWARE.backlog.apps.dashboard.20131028-1014.xlsx [2]: https://forge.fi-ware.eu/docman/view.php/27/2950/FIWARE.backlog.cloud.dashboard.20131028-1014.xlsx [3]: https://forge.fi-ware.eu/docman/view.php/27/2953/FIWARE.backlog.iot.dashboard.20131028-1014.xlsx [4]: https://forge.fi-ware.eu/docman/view.php/27/2951/FIWARE.backlog.data.dashboard.20131028-1014.xlsx [5]: https://forge.fi-ware.eu/docman/view.php/27/2952/FIWARE.backlog.i2nd.dashboard.20131028-1014.xlsx [6]: https://forge.fi-ware.eu/docman/view.php/27/2954/FIWARE.backlog.security.dashboard.20131028-1014.xlsx Reviews: WP3-Apps [7]; WP4-Cloud [8]; WP5-IoT [9]; WP6-Data [10]; WP7-I2nd [11]; WP8-Sec [12] [7]: https://forge.fi-ware.eu/docman/view.php/27/2943/FIWARE.backlog.apps.review.20131028-0856.xlsx [8]: https://forge.fi-ware.eu/docman/view.php/27/2944/FIWARE.backlog.cloud.review.20131028-0857.xlsx [9]: https://forge.fi-ware.eu/docman/view.php/27/2947/FIWARE.backlog.iot.review.20131028-0857.xlsx [10]: https://forge.fi-ware.eu/docman/view.php/27/2945/FIWARE.backlog.data.review.20131028-0857.xlsx [11]: https://forge.fi-ware.eu/docman/view.php/27/2946/FIWARE.backlog.i2nd.review.20131028-0857.xlsx [12]: https://forge.fi-ware.eu/docman/view.php/27/2948/FIWARE.backlog.security.review.20131028-0858.xlsx ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 18435 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 37719 bytes Desc: image002.png URL: From thorsten.sandfuchs at sap.com Tue Oct 29 10:10:24 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 29 Oct 2013 09:10:24 +0000 Subject: [Fiware-wpl] FW: Your message to Fiware-wpa awaits moderator approval In-Reply-To: References: Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486067E5E@DEWDFEMB11A.global.corp.sap> Who is responsible for approving messages to the lists, if miguel is on holiday? Why are we not possible to post on the lists? Thanks for letting me know, /Thorsten -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] Sent: Dienstag, 29. Oktober 2013 08:59 To: Sandfuchs, Thorsten Subject: Your message to Fiware-wpa awaits moderator approval Your mail to 'Fiware-wpa' with the subject RE: [Fiware-testbed] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. Is being held until the list moderator can review it for approval. The reason it is being held: Too many recipients to the message Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: From mev at tid.es Tue Oct 29 11:41:50 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 29 Oct 2013 10:41:50 +0000 Subject: [Fiware-wpl] FW: Your message to Fiware-wpa awaits moderator approval In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486067E5E@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486067E5E@DEWDFEMB11A.global.corp.sap> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E638F@EX10-MB2-MAD.hi.inet> I'll try to fix it Manuel -----Original Message----- From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: martes, 29 de octubre de 2013 10:10 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] FW: Your message to Fiware-wpa awaits moderator approval Who is responsible for approving messages to the lists, if miguel is on holiday? Why are we not possible to post on the lists? Thanks for letting me know, /Thorsten -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] Sent: Dienstag, 29. Oktober 2013 08:59 To: Sandfuchs, Thorsten Subject: Your message to Fiware-wpa awaits moderator approval Your mail to 'Fiware-wpa' with the subject RE: [Fiware-testbed] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. Is being held until the list moderator can review it for approval. The reason it is being held: Too many recipients to the message Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Wed Oct 30 07:55:26 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 30 Oct 2013 07:55:26 +0100 Subject: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration --> request for update In-Reply-To: <393554EDCF801348BC53C7813C6CB73B1A6821C5@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B1A6821C5@DEWDFEMB14A.global.corp.sap> Message-ID: <5270AD5E.2040801@tid.es> Hi, I was writing an email on the matter, but I have found it is actually helpful to structure the message in response to your email, so here you are: On 28/10/13 14:31, Heller, Markus wrote: Dear Juanjo, Since we did not have the WPL/WPA call today, I would like to address the FI-WARE project extension topic here. If I am right, you wrote in one of your mails on this that you have intended to send a consortium statement message to EC at end of the last week. Can I please ask you for an update on the discussed FI-WARE Extension topic and how we plan to drive this forward? Since we didn't reach a consensus, I haven't sent anything yet to the EC of course. Additionally, I have the following questions on this topic: 1. Do we have an answer from EC /reviewers for the question who requested it (EC, reviewers, both) and what they think should be done/improved in the extension period? If I recall tight, there was an action item either in one of the PCC call / WPL&WPA call on this. I have made the request for a more detailed explanation about this request by the EC+reviewers during a conversation I had with Arian and Jes?s Villasante this monday but I was planning to send a formal request before the end of today. It would be actually helpful if you provide a first version of the questions you would like to get answered so that I can secure that I formulate a complete set of questions. Otherwise, we may end up with an answer that may be satisfactory to me but not complete by SAP. Please provide such a text proposal along today, otherwise I will formulate the question with my best understanding of what kind of answers SAP wishes to see. During this conversation, the EC made it very clear to me that they WANT this extension. I also understood they believe this extension is required to be able to execute the readjustments they anticipate as a result of the assessment on GEs they have announced they will carry out in the month 30 review. As you may remember, the last review report announced that this GE assessment will be carried out in the month 30 review and reallocation of resources will be derived from it (as mentioned in the outcome review report ... "The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project"). Therefore, I understand from my conversation with Arian and Jesus that one of the reasons the EC require this extension is to be able to implement the necessary changes derived from these decisions. But better to get a formal answer. They even mentioned at that time that objection to the extension may be considered a matter of non-performance of the contract by the objecting partners (this I guess only if the extension becomes an actual request, rather than a recommendation, as a result of the month 30 review). BTW, during the conversation the EC also confirmed that the several inputs they will consider for driving the decisions on the assessments of the GEs would be: * individual exploitation plans of the owners of the GEis linked to a GE * expected usage by UC projects as captured on the FI-PPP cockpit on "FI-WARE GEis Planned Usage and General Information" * the own assessment mady by the reviewers * report made by Lutz Schubert * experience using the GEis during hackathons or by any other parties (e.g., usage by research projects planning to use FI-LAB) 2. As I have understood in my other mails, some other partners also sent a "rather not" message to you like we did (but most tied it to a statement like "if all others go for it we would maybe join in"). Do you have an current overview who prefers to either go for an extension or to not go for an extension - e.g. on the WPL/WPA mailing list? What I have planned to do is a poll among the partners, so that we have a clear picture of who really objects (under any formula), who can live with it but provided some restrictions apply, who can go for it and actually prefer to go for it, etc. 3. Time Frame: Do we (still) talk about a possible extension of 4 months - or has something changed in the meantime w.r.t. extension time frame? I once got the rumor that the EC wanted to get the project extended for a longer period, but this possibility was not mentioned during the conversation with the EC this monday. It seems like an extension of 4 months would work for them. My personal feeling is that if we post-pone acceptance of an extension, this extension will be forced as a result of the month 30 review and then the request may be for a longer period ... so better not to allow this to happen and go for negotiating an extension of 4 months ... but just my personal feeling. 4. Budget for extension: Would the extension be somewhat budget-neutral or would the extension come with any additional funding? Of course, I guess the extension would be budget-neutral, right? This question maybe has been already addressed during my vacation... The extension would not come with any additional funding. Torsten shared our current SAP opinion on a possible extension below and I would also be interested in your opinion on his reply to you given below, for example, how such a mixed approach (some partners stay vs. some partners leave) can be organized with a detail plan to make sure the split-up really works out well to avoid last mile damage to the project due to failing handovers or necessary result reductions etc... I can generally understand some of the points you made, but frankly speaking I cannot share why a single partner can block other partners for going to such an extension if those other partners can live with it or wish to. I believe it should be feasible, as I mentioned in my reply to Torsten, to plan things so that some partners can leave the project if they cannot live with the extension (which is something I can understand) so the software of the GEis they own gets frozen and, in addition, we plan how others can take over any coordination activity the may be doing. Why objecting to that and create a big issue to the project ? This is honestly something I cannot understand. Now, I add, based on my feelings from my conversation with Jesus an Arian, that going this direction can be worse even for the objecting partner ... but just my personal feelings again. If you agree, we can try to go on with e-mail during the week to bring the topic forward since there is no other coordination call currently scheduled this week if I see right. I agree. Let's try to make progress on the discussion off-line so we progress before the next coordination call next Monday, November 4th. Cheers, -- Juanjo Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: Donnerstag, 24. Oktober 2013 11:33 To: Juanjo Hierro Cc: Theilmann, Wolfgang; 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu'; Nochta, Zoltan Subject: Re: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration Dear Juanjo, We still don't understand why the extension is necessary esp. what's the intention of the EC/Reviewers, what do they expect to improve during the extension time. Your proposal to let SAP close its activities and deliverables following the original plan does not really work out well. There are many dependencies we have to sort out to let us work independently. Also we would properly not longer serve as a WPL/WPA for WP3. That's why we insist in a more detailed plan then just moving deliverables a few months. Regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen ________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: Thursday, October 24, 2013 11:09 AM To: Leidig, Torsten Cc: 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu'; Nochta, Zoltan; Theilmann, Wolfgang Subject: Re: [Fiware-wpa] IMPORTANT: Extension of the project duration Dear Torsten, I believe that nothing prevents that a given partner, or even a whole chapter, ends its work and submit their deliverables as defined in the original DoW. That would mean submitting in advance, which would not be that much an issue ... In other words, I don't have an issue if SAP closes its activities and deliverables following the original plan, while other chapter/partners keep working and deliver after closing release 3.3, planned by end of April (check [1]) ... would that work with you ? On the other hand ... Is this the sole position of SAP in WP3, or extension is an issue also for the rest of partners in the WP ? ... and BTW, for many of the deliverables that have to do with software release, specifications, software documentation (i.e., the more heavy ones) delivery dates are month 33, which means end of January 2014 ... so there are no 6 months from now but really 3 months ! Best regards, -- Juanjo [1] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates On 23/10/13 14:23, Leidig, Torsten wrote: Dear Juanjo, This is to inform you that SAP objects to the suggested extension of the FI-WARE project for a number of reasons: * We expect to finalize all our WP deliverables until end of April. * We also expect to deliver all contributions to general deliverables. * SAP internal resource, planning, and contractual constraints will not allow us to do substantial work after the original project end. Therefore an extension is counter productive. * We are seriously concerned that an extension will further delay the project. We don't understand why deliverables cannot be finalized and why. Just moving the deadlines is not enough to do a proper re-planning. We cannot estimate, which workload is imposed on us during this extension period. Please also be aware that 2 month of the extension fall into summer period, where usually not much happens. * The EC did not express a clear explanation, why they suggest an extension. The comments in the review report are very vague. We also don't understand why so many deliverables have to be moved 4 months. Is this really necessary? The approach should be to focus and get most of the deliverables ready at the original project end (We still have 6 month to work on it!) and leave only a very small number of deliverables for a possible extension. Also not all WP and partners might be necessary during this extension. Best regards, Torsten Leidig Dr. Torsten Leidig Research Expert Human Computer Interaction TIP PA&TS HCI Research SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7-52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, L?o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Oct 30 08:08:16 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 30 Oct 2013 08:08:16 +0100 Subject: [Fiware-wpl] VERY URGENT AND IMPORTANT: Dates for month 30 review Message-ID: <5270B060.6070802@tid.es> Hi all, During the call that I have with Jesus Villasante and Arian, it was agreed to delay the dates for the month 30 review to the week of December 18th. Then, we need to urgently close the final date we would like to propose. My preference would be to go for Wednesday 20th so that we have two re-hearsal days on 18 and 19. I have setup a doodle for choosing the most suitable date at: http://www.doodle.com/qfayw7dne8f6d7qn Please answer along today so that I can send an official answer tomorrow morning. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Oct 30 08:39:17 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 30 Oct 2013 08:39:17 +0100 Subject: [Fiware-wpl] R: VERY URGENT AND IMPORTANT: Dates for month 30 review In-Reply-To: <5270B060.6070802@tid.es> References: <5270B060.6070802@tid.es> Message-ID: Hi Juanjo, I expressed my vote in the doodle, assuming that your preference for the day of review goes to *Friday* 20th, and the doodle is mainly to check the presence for the rehearsal, is this correct? BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 30 ottobre 2013 08:08 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] VERY URGENT AND IMPORTANT: Dates for month 30 review Hi all, During the call that I have with Jesus Villasante and Arian, it was agreed to delay the dates for the month 30 review to the week of December 18th. Then, we need to urgently close the final date we would like to propose. My preference would be to go for Wednesday 20th so that we have two re-hearsal days on 18 and 19. I have setup a doodle for choosing the most suitable date at: http://www.doodle.com/qfayw7dne8f6d7qn Please answer along today so that I can send an official answer tomorrow morning. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From GLIKSON at il.ibm.com Wed Oct 30 08:52:29 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 30 Oct 2013 09:52:29 +0200 Subject: [Fiware-wpl] R: VERY URGENT AND IMPORTANT: Dates for month 30 review In-Reply-To: References: <5270B060.6070802@tid.es> Message-ID: Indeed, December 18th is mid-week, and 20th is Friday.. Was this the intention? Can you, please, clarify? Alex From: Garino Pierangelo To: Juanjo Hierro , Cc: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 30/10/2013 09:39 AM Subject: [Fiware-wpl] R: VERY URGENT AND IMPORTANT: Dates for month 30 review Sent by: fiware-wpl-bounces at lists.fi-ware.eu Hi Juanjo, I expressed my vote in the doodle, assuming that your preference for the day of review goes to *Friday* 20th, and the doodle is mainly to check the presence for the rehearsal, is this correct? BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [ mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 30 ottobre 2013 08:08 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] VERY URGENT AND IMPORTANT: Dates for month 30 review Hi all, During the call that I have with Jesus Villasante and Arian, it was agreed to delay the dates for the month 30 review to the week of December 18th. Then, we need to urgently close the final date we would like to propose. My preference would be to go for Wednesday 20th so that we have two re-hearsal days on 18 and 19. I have setup a doodle for choosing the most suitable date at: http://www.doodle.com/qfayw7dne8f6d7qn Please answer along today so that I can send an official answer tomorrow morning. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From jhierro at tid.es Wed Oct 30 11:37:41 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 30 Oct 2013 11:37:41 +0100 Subject: [Fiware-wpl] VERY URGENT AND IMPORTANT: Dates for month 30 review In-Reply-To: <5270B060.6070802@tid.es> References: <5270B060.6070802@tid.es> Message-ID: <5270E175.4020805@tid.es> Hi all, Obviously I brought wrong dates in the body of my message. The week of December 16th is the week to go. Nevertheless, the dates were correctly listed in the doodle poll. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 30/10/13 08:08, Juanjo Hierro wrote: Hi all, During the call that I have with Jesus Villasante and Arian, it was agreed to delay the dates for the month 30 review to the week of December 18th. Then, we need to urgently close the final date we would like to propose. My preference would be to go for Wednesday 20th so that we have two re-hearsal days on 18 and 19. I have setup a doodle for choosing the most suitable date at: http://www.doodle.com/qfayw7dne8f6d7qn Please answer along today so that I can send an official answer tomorrow morning. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Wed Oct 30 13:08:32 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Wed, 30 Oct 2013 13:08:32 +0100 Subject: [Fiware-wpl] VERY URGENT AND IMPORTANT: Dates for month 30 review In-Reply-To: <5270E175.4020805@tid.es> References: <5270B060.6070802@tid.es> <5270E175.4020805@tid.es> Message-ID: dear juanjo, i expressed my dates in the doodle. please consider that 20th is inconvenient for our friends from israel, but also for all of us as planes from brussels are already mostly booked .... most people will leave brussels to have the xmas holidays elsewhere .... if it is in madrid at least we solve the last issue, but please move a day before ciao, stefano 2013/10/30 Juanjo Hierro : > Hi all, > > Obviously I brought wrong dates in the body of my message. The week of > December 16th is the week to go. > > Nevertheless, the dates were correctly listed in the doodle poll. > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > FI-PPP Architecture Board chairman > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > On 30/10/13 08:08, Juanjo Hierro wrote: > > Hi all, > > During the call that I have with Jesus Villasante and Arian, it was agreed > to delay the dates for the month 30 review to the week of December 18th. > > Then, we need to urgently close the final date we would like to propose. > My preference would be to go for Wednesday 20th so that we have two > re-hearsal days on 18 and 19. > > I have setup a doodle for choosing the most suitable date at: > > http://www.doodle.com/qfayw7dne8f6d7qn > > > Please answer along today so that I can send an official answer tomorrow > morning. > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > FI-PPP Architecture Board chairman > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 From markus.heller at sap.com Wed Oct 30 19:09:42 2013 From: markus.heller at sap.com (Heller, Markus) Date: Wed, 30 Oct 2013 18:09:42 +0000 Subject: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration --> request for update In-Reply-To: <5270AD5E.2040801@tid.es> References: <393554EDCF801348BC53C7813C6CB73B1A6821C5@DEWDFEMB14A.global.corp.sap> <5270AD5E.2040801@tid.es> Message-ID: <393554EDCF801348BC53C7813C6CB73B1A683C4C@DEWDFEMB14A.global.corp.sap> Hi Juanjo, Sorry for my late answer today... First, thanks so far for answering to my mail and trying to provide some more insight for me/us based on your talks with the EC. > Please provide such a text proposal along today, otherwise I will formulate the question with my best understanding of what kind of answers SAP wishes to see. Please go ahead and send the questions. From my side I would like to understand why the extension is necessary esp. what is the intention of the EC and/or Reviewers insofar as what they expect to improve during the extension time w.r.t to concrete missing results or expected activities to be carried out. Please let me also explain our last week's "objection" that you address in your mail: our objection was meant in the "historic" context of the last week - to object against your plan to send the mail to Arian last week (after having proposed this 2 days before). The objection shall be seen restricted to that past time. We had answered your mail with request for partner opinions and expressed we would certainly due to missing information and some identified problems would not vote "pro-extension". To illustrate this, we additionally shared a list of problems / doubts with the WPL/WPA team. For example, Torsten stated also "That's why we insist in a more detailed plan then just moving deliverables a few months." which underlined this. Let me therefore clearly express that as of today we do not block a "fi-ware extension _per se_". I would be happy if we could take my statement for now and move on in the ongoing discussion. For instance, we now need more details/answers to questions like "why extension needed", "what do we need to carry out - partner-wise", etc. either answered by EC and also answered among ourselves. We have the position that we in FI-WARE need to achieve a consortium-wide opinion or agreement (e.g. like the doodle that you plan). For example, a pressing interesting topic for me is info about "can individual partners leave and how to handle this / how to sort this out?" which needs to be clarified now, at least for me, and you took this up in your mail likewise. My most dominant issue is still lack of EC-side information to all partners which we can use, e.g. in a written form or such to be able to analyze comprehend a possible standpoint. Up to now, EC did not express a clear (written) explanation of intentions and expectations to partners (only phone calls or other informal talks, I might have missed something indeed). So for me only now clouds are beginning to fade away a bit, e.g. with the info from your mail below. In this respect, I am looking forward to Arians answer to the request you are about to send to him soon. Having said this, I agree with you that a good next step is to execute the Doodle to assess the opinion of all partners to get a good starting point (I did this poll in the WP3 chapter already, inspired by one of your comments before, and I could share the results if needed, but not all partners have answered). That is why I here do not go and answer to other aspects in your answer and would like to wait until I get a better picture. Best wishes Markus From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Mittwoch, 30. Oktober 2013 07:55 To: Heller, Markus Cc: 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu' Subject: Re: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration --> request for update Hi, I was writing an email on the matter, but I have found it is actually helpful to structure the message in response to your email, so here you are: On 28/10/13 14:31, Heller, Markus wrote: Dear Juanjo, Since we did not have the WPL/WPA call today, I would like to address the FI-WARE project extension topic here. If I am right, you wrote in one of your mails on this that you have intended to send a consortium statement message to EC at end of the last week. Can I please ask you for an update on the discussed FI-WARE Extension topic and how we plan to drive this forward? Since we didn't reach a consensus, I haven't sent anything yet to the EC of course. Additionally, I have the following questions on this topic: 1. Do we have an answer from EC /reviewers for the question who requested it (EC, reviewers, both) and what they think should be done/improved in the extension period? If I recall tight, there was an action item either in one of the PCC call / WPL&WPA call on this. I have made the request for a more detailed explanation about this request by the EC+reviewers during a conversation I had with Arian and Jes?s Villasante this monday but I was planning to send a formal request before the end of today. It would be actually helpful if you provide a first version of the questions you would like to get answered so that I can secure that I formulate a complete set of questions. Otherwise, we may end up with an answer that may be satisfactory to me but not complete by SAP. Please provide such a text proposal along today, otherwise I will formulate the question with my best understanding of what kind of answers SAP wishes to see. During this conversation, the EC made it very clear to me that they WANT this extension. I also understood they believe this extension is required to be able to execute the readjustments they anticipate as a result of the assessment on GEs they have announced they will carry out in the month 30 review. As you may remember, the last review report announced that this GE assessment will be carried out in the month 30 review and reallocation of resources will be derived from it (as mentioned in the outcome review report ... "The result of this evaluation is that the prospects for future use of GE implementations will be assessed. It may lead to decisions to stop funding certain activities and allocate scarce funds to more promising areas for the remainder of the project"). Therefore, I understand from my conversation with Arian and Jesus that one of the reasons the EC require this extension is to be able to implement the necessary changes derived from these decisions. But better to get a formal answer. They even mentioned at that time that objection to the extension may be considered a matter of non-performance of the contract by the objecting partners (this I guess only if the extension becomes an actual request, rather than a recommendation, as a result of the month 30 review). BTW, during the conversation the EC also confirmed that the several inputs they will consider for driving the decisions on the assessments of the GEs would be: * individual exploitation plans of the owners of the GEis linked to a GE * expected usage by UC projects as captured on the FI-PPP cockpit on "FI-WARE GEis Planned Usage and General Information" * the own assessment mady by the reviewers * report made by Lutz Schubert * experience using the GEis during hackathons or by any other parties (e.g., usage by research projects planning to use FI-LAB) 2. As I have understood in my other mails, some other partners also sent a "rather not" message to you like we did (but most tied it to a statement like "if all others go for it we would maybe join in"). Do you have an current overview who prefers to either go for an extension or to not go for an extension - e.g. on the WPL/WPA mailing list? What I have planned to do is a poll among the partners, so that we have a clear picture of who really objects (under any formula), who can live with it but provided some restrictions apply, who can go for it and actually prefer to go for it, etc. 3. Time Frame: Do we (still) talk about a possible extension of 4 months - or has something changed in the meantime w.r.t. extension time frame? I once got the rumor that the EC wanted to get the project extended for a longer period, but this possibility was not mentioned during the conversation with the EC this monday. It seems like an extension of 4 months would work for them. My personal feeling is that if we post-pone acceptance of an extension, this extension will be forced as a result of the month 30 review and then the request may be for a longer period ... so better not to allow this to happen and go for negotiating an extension of 4 months ... but just my personal feeling. 4. Budget for extension: Would the extension be somewhat budget-neutral or would the extension come with any additional funding? Of course, I guess the extension would be budget-neutral, right? This question maybe has been already addressed during my vacation... The extension would not come with any additional funding. Torsten shared our current SAP opinion on a possible extension below and I would also be interested in your opinion on his reply to you given below, for example, how such a mixed approach (some partners stay vs. some partners leave) can be organized with a detail plan to make sure the split-up really works out well to avoid last mile damage to the project due to failing handovers or necessary result reductions etc... I can generally understand some of the points you made, but frankly speaking I cannot share why a single partner can block other partners for going to such an extension if those other partners can live with it or wish to. I believe it should be feasible, as I mentioned in my reply to Torsten, to plan things so that some partners can leave the project if they cannot live with the extension (which is something I can understand) so the software of the GEis they own gets frozen and, in addition, we plan how others can take over any coordination activity the may be doing. Why objecting to that and create a big issue to the project ? This is honestly something I cannot understand. Now, I add, based on my feelings from my conversation with Jesus an Arian, that going this direction can be worse even for the objecting partner ... but just my personal feelings again. If you agree, we can try to go on with e-mail during the week to bring the topic forward since there is no other coordination call currently scheduled this week if I see right. I agree. Let's try to make progress on the discussion off-line so we progress before the next coordination call next Monday, November 4th. Cheers, -- Juanjo Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: Donnerstag, 24. Oktober 2013 11:33 To: Juanjo Hierro Cc: Theilmann, Wolfgang; 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu'; Nochta, Zoltan Subject: Re: [Fiware-wpl] [Fiware-wpa] IMPORTANT: Extension of the project duration Dear Juanjo, We still don't understand why the extension is necessary esp. what's the intention of the EC/Reviewers, what do they expect to improve during the extension time. Your proposal to let SAP close its activities and deliverables following the original plan does not really work out well. There are many dependencies we have to sort out to let us work independently. Also we would properly not longer serve as a WPL/WPA for WP3. That's why we insist in a more detailed plan then just moving deliverables a few months. Regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen ________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: Thursday, October 24, 2013 11:09 AM To: Leidig, Torsten Cc: 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu'; Nochta, Zoltan; Theilmann, Wolfgang Subject: Re: [Fiware-wpa] IMPORTANT: Extension of the project duration Dear Torsten, I believe that nothing prevents that a given partner, or even a whole chapter, ends its work and submit their deliverables as defined in the original DoW. That would mean submitting in advance, which would not be that much an issue ... In other words, I don't have an issue if SAP closes its activities and deliverables following the original plan, while other chapter/partners keep working and deliver after closing release 3.3, planned by end of April (check [1]) ... would that work with you ? On the other hand ... Is this the sole position of SAP in WP3, or extension is an issue also for the rest of partners in the WP ? ... and BTW, for many of the deliverables that have to do with software release, specifications, software documentation (i.e., the more heavy ones) delivery dates are month 33, which means end of January 2014 ... so there are no 6 months from now but really 3 months ! Best regards, -- Juanjo [1] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates On 23/10/13 14:23, Leidig, Torsten wrote: Dear Juanjo, This is to inform you that SAP objects to the suggested extension of the FI-WARE project for a number of reasons: * We expect to finalize all our WP deliverables until end of April. * We also expect to deliver all contributions to general deliverables. * SAP internal resource, planning, and contractual constraints will not allow us to do substantial work after the original project end. Therefore an extension is counter productive. * We are seriously concerned that an extension will further delay the project. We don't understand why deliverables cannot be finalized and why. Just moving the deadlines is not enough to do a proper re-planning. We cannot estimate, which workload is imposed on us during this extension period. Please also be aware that 2 month of the extension fall into summer period, where usually not much happens. * The EC did not express a clear explanation, why they suggest an extension. The comments in the review report are very vague. We also don't understand why so many deliverables have to be moved 4 months. Is this really necessary? The approach should be to focus and get most of the deliverables ready at the original project end (We still have 6 month to work on it!) and leave only a very small number of deliverables for a possible extension. Also not all WP and partners might be necessary during this extension. Best regards, Torsten Leidig Dr. Torsten Leidig Research Expert Human Computer Interaction TIP PA&TS HCI Research SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7-52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, L?o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Wed Oct 30 19:49:32 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Wed, 30 Oct 2013 19:49:32 +0100 Subject: [Fiware-wpl] catalogue status Message-ID: dear juanjo and all, i'd like to put to your attention the current situation of the catalogue, certainly the main fi-ware window to the general public. as it stands at the moment (attached the status file) the progress is not satisfactory at all although several colleagues worked to improve their entries in the catalogue. ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- A non-text attachment was scrubbed... Name: Testbed-V2_catalogue_publication_status.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 39286 bytes Desc: not available URL: From jhierro at tid.es Wed Oct 30 22:09:12 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 30 Oct 2013 22:09:12 +0100 Subject: [Fiware-wpl] [Fiware-wpa] VERY URGENT AND IMPORTANT: Dates for month 30 review In-Reply-To: <5270B060.6070802@tid.es> References: <5270B060.6070802@tid.es> Message-ID: <52717578.2020504@tid.es> Hi all, Final clarifications: * The review meeting would take place in Brussels. * Again I clarify that the dates I mentioned in the body of my email were to select the day for the review. They were properly defined in the poll. We would ask for a rehearsal the full day before (starting at 09:00am) or, if it is suitable to all, one day and a half before (i.e., starting at 13:00 CET on Monday if the review is on Wednesday or 13:00 CET on Tuesday if the review is on Thursday) Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 30/10/13 08:08, Juanjo Hierro wrote: Hi all, During the call that I have with Jesus Villasante and Arian, it was agreed to delay the dates for the month 30 review to the week of December 18th. Then, we need to urgently close the final date we would like to propose. My preference would be to go for Wednesday 20th so that we have two re-hearsal days on 18 and 19. I have setup a doodle for choosing the most suitable date at: http://www.doodle.com/qfayw7dne8f6d7qn Please answer along today so that I can send an official answer tomorrow morning. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Thu Oct 31 08:56:13 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 31 Oct 2013 07:56:13 +0000 Subject: [Fiware-wpl] Agile dynamic - closing sprint 3.2.1 - snapshort at 18:00 Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E8950@EX10-MB2-MAD.hi.inet> Dear Partners, Let me remind you of today's closing of sprint 3.2.1. At 18:00 CET, I'll get the snapshot. Please, take your 5 minutes to update your backlog's items status. Thanks for cooperation!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Thu Oct 31 21:49:08 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Thu, 31 Oct 2013 21:49:08 +0100 Subject: [Fiware-wpl] [Fiware-wpa] VERY URGENT AND IMPORTANT: Dates for month 30 review In-Reply-To: <5270B060.6070802@tid.es> References: <5270B060.6070802@tid.es> Message-ID: <4021_1383252529_5272C231_4021_6757_1_6fe6e1d6-8643-4cb3-9914-954323aeee73@THSONEA01HUB05P.one.grp> Dear Juanjo We agree, Pascal and me for Wednesday 20th (review). Best regards Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 30 octobre 2013 08:08 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] VERY URGENT AND IMPORTANT: Dates for month 30 review Hi all, During the call that I have with Jesus Villasante and Arian, it was agreed to delay the dates for the month 30 review to the week of December 18th. Then, we need to urgently close the final date we would like to propose. My preference would be to go for Wednesday 20th so that we have two re-hearsal days on 18 and 19. I have setup a doodle for choosing the most suitable date at: http://www.doodle.com/qfayw7dne8f6d7qn Please answer along today so that I can send an official answer tomorrow morning. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Thu Oct 31 23:03:47 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Thu, 31 Oct 2013 23:03:47 +0100 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - WP8 Security Message-ID: <4021_1383257032_5272D3C8_4021_7203_1_aaa31e85-ff5d-40b6-aa11-5fa2601b05fb@THSONEA01HUB03P.one.grp> Dear All, Please find enclosed the current version of the periodic report for WP8 Security Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D 1 2 5 - WP8_2013-10-31.doc Type: application/msword Size: 279552 bytes Desc: D 1 2 5 - WP8_2013-10-31.doc URL: From daniel.gidoin at thalesgroup.com Mon Oct 28 09:16:59 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Mon, 28 Oct 2013 09:16:59 +0100 Subject: [Fiware-wpl] Joint WPLs/WPAs follow-up confcall (Part II) In-Reply-To: <936DECD07EB54B4BAA44E7B823EC89418537EB9A@EX10-MB2-MAD.hi.inet> References: <936DECD07EB54B4BAA44E7B823EC89418537EB9A@EX10-MB2-MAD.hi.inet> Message-ID: <1793_1382948214_526E1D76_1793_64_1_8F1D40232A0E68409E3FC23A30C326620168D2F2C758@THSONEA01CMS04P.one.grp> Dear Juan Jose, I apologize but I am sadly unwell and I will not take part in confcalls today Best regards Daniel -----Rendez-vous d'origine----- De : JUAN JOSE HIERRO SUREDA [mailto:jhierro at tid.es] Envoy? : lundi 28 octobre 2013 00:57 ? : fiware-wpl at lists.fi-ware.eu; Sandfuchs, Thorsten; MANUEL ESCRICHE VICENTE; fiware-wpa at lists.fi-ware.eu Cc : Leidig, Torsten; JOSE JIMENEZ DELGADO; MIGUEL CARRILLO PACHECO; Nuria De-Lama Sanchez; Hans.Einsiedler at telekom.de; Thomas M. Bohnert ; Alex Glikson/Haifa/IBM; Marti Christof (mach); Garino Pierangelo; Heller, Markus; SERGIO GARCIA GOMEZ; NAGELLEN Thierry OLNC/OLPS Objet : [Fiware-wpa] Canceled: Joint WPLs/WPAs follow-up confcall (Part II) Date : lundi 28 octobre 2013 14:30-16:00 (GMT+01:00) Bruxelles, Copenhague, Madrid, Paris. O? : Joint WPLs/WPAs follow-up confcalls are split into two parts. This is the second one and we will always stick to the end time. Topics not addressed in the first slot will be treated in this slot of the afternoon. This slot will also be used to also address Technical-Architecture issues. We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx << Fichier: ATT00001.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From Richard.Egan at uk.thalesgroup.com Thu Oct 31 12:03:25 2013 From: Richard.Egan at uk.thalesgroup.com (EGAN Richard) Date: Thu, 31 Oct 2013 11:03:25 +0000 Subject: [Fiware-wpl] FI-WARE Progress Report - THALES input (to your WP Progress Report) In-Reply-To: References: Message-ID: <7C80A1EAA66A4F45BA3A574774382B9BA99A0D1327@THSONEP02CMB01P.one-02-priv.grp> Dear WP Leads (especially WP10, 11 & 12) I have attached an updated version of the Thales contribution with some more details. Tracked changes were used so the updates are visible. Richard Richard Egan Technical Manager, Research & Technology Thales UK Worton Drive, Reading, Berkshire, RG2 0SB www.thalesgroup.com/uk Tel: +44 (0)118 923 8375. Mob: +44 (0)79 71 32 99 28. Fax: +44 (0) 118 923 8399. e-mail: richard.egan at uk.thalesgroup.com From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: 26 October 2013 10:45 To: fiware-wpl at lists.fi-ware.eu Cc: BISSON Pascal; GIDOIN Daniel; SIEUX Corinne; CHALLAMEL Remi; EGAN Richard; CHATEL Pierre; BESSON Lionel; LOPEZ RAMOS Mario; Juanjo Hierro; JAVIER DE PEDRO SANCHEZ; Stefano.depanfilis at eng.it; GASPARD Lucie Subject: FI-WARE Progress Report - THALES input (to your WP Progress Report) Importance: High Dear WP Lead colleagues, Please find attached to this email the Thales wide input - as per today - to Progress Report M25-M30. This in order for you to use and take out of it what needs to go for Thales at the level of the Progress Report of the WP you lead. FYI I would be on vacation next week but Daniel (in cc) would replace me. As for the missing contrib. at WP4 and WP3 level I count on Lionel/Mario and Pierre as participants to these WPs to send them to WP4 Lead (Alex) and WP3 Lead (Markus) asap and cc me/Daniel/Corinne. Best Regards, Pascal PS: I put Thales colleagues involved in your WP in cc of that email for their information also records.s -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Tue Oct 29 08:58:15 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 29 Oct 2013 07:58:15 +0000 Subject: [Fiware-wpl] [Fiware-testbed] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486060DDF@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486060DDF@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486067C00@DEWDFEMB11A.global.corp.sap> Thanks to the cloud chapter which actually managed to contribute as planned. May I kindly ask what the other WPL/WPAs are envisioning for the final submission? Do you need more time or are you planning to not submit at all? Would you be in favor of shifting the deliverable deadline because of missing contributions and communicating this to the EC or do you think we should submit, even if a WP did not provide a contribution? Thanks for any comments. /Thorsten From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 24. Oktober 2013 09:26 To: Leidig, Torsten; BISSON Pascal; Heller, Markus; daniel.gidoin at thalesgroup.com; ralli at tid.es; GLIKSON at il.ibm.com; sergg at tid.es; thierry.nagellen at orange.com Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu Subject: [Fiware-testbed] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. Dear WPL & WPA colleagues (apps, cloud, data, iot, security), as planned below I would like to encourage and ask kindly for your contributions to the validation deliverable, which for your chapter the Testbed Team prepared as attached & in the testbed wiki. You will find the task for "your" chapter described in the doc - the section you have to fill is "Comments by WP leadership" for your chapter and should roughly cover answers to the questions, which I as well printed at the bottom of this email. These questions might help you find relevant and "interesting" things, the Reviews would like to know in relation to our "answer" to the validation of the use cases in phase 1. Please either directly change the DOC-file with "tracked"-changes - or contribute to the wiki where all pages from this deliverable are linked here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page#Structure_of_this_Document Please finish this task until Monday, 28.10. EOB the latest. If you have any questions, please don't hesitate to ask! Thanks a lot and best regards /Thorsten Questions to be answered by WPL/WPA * What went good, what went bad during this validation? * What was the recent actions implemented which address potential challenges identified during the validation? * Which challenges did you mainly identify, coming out of this validation? * What strength can you find for your chapter and how to further build upon this strength? * What measures did you take to mitigate the situation? * Overall acceptance over all validated GE for your chapter? (find answer Q.GE.11) * How deep have they been validated for your chapter? (find answer QGE.13) * Browse through the "scenario-based answers" (doc-files) and extract some relevant quotes good ones and bad ones, touching on your chapter GEs. - the doc files are linked here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Overview_FI-WARE_validation#Validation_of_non-functional_requirements * What would you do differently in the next validation round? * What would you find interesting from the use cases to better improve the validation? De : fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] De la part de Sandfuchs, Thorsten Envoy? : lundi 14 octobre 2013 10:25 ? : fiware-testbed at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-testbed] Minutes and action points on validation deliverable submission (10.5.2b) Dear colleagues, on Friday there was a testbed-internal session which discussed how to submit D.10.5.2b (the resubmission of the validation deliverable). We have a very tight schedule to submit this deliverable with all contributions in time. For this minutes I'm taking WPL/WPA on the CC list in order to let everybody know the status. Thorsten presented the approach and explained along the lines of the presentation what content should needs to be produced. - Mainly the testbed-team will in a neutral way write what we "see", judged by the numbers - things like: "SMARTAGRIFOOD rated the integration badly in the case of the XXX chapter...." We could try to come up with first assumptions on why these ratings did take place and dig deeper - but overall WPL/WPA need to do the _content_ driven analysis. "The reason for this was ..." or "We will take this serious and already implemented the following actions ..." Background are the graphs and tables prepared by Thorsten in the presentation and pivot-tables of the XLS. - Additionally and for the deliverable the "scenario based" questionnairs in DOC format need to be analyzed and "highs" and "lows" need to be extracted for the chapters. - Stefano wanted everybody to analyze the bare-metal XLS and try to come up with "new interesting" things somebody sees in the day. This task needs to be worked on in parallel within the week of 14.10. - 18.10. - everybody to report relevant findings on the 22.10. Rough time plan: KW42 (14.-18.10): main content work, Testbed-team writing what we "see", judged by the numbers KW43 (21.-25.10): finalizing text & hand-over to WPL/WPA team - 22th of October: deadline for the content work - goal: on 23th October WPL/WPA should be able to start their work with the content analysis (you will have ~3 business days) KW44 (28.-30.10): finalizing the DOC deliverable and starting a review cycle - Please volunteer if you want to be a reviewer for this deliverable KW44 (31.10): planned submission to EC Please - if possible - directly update the wiki : https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page#Structure_of_this_Document or the underlying pages. If unsure, just write the text in any other format and provide it ASAP to Thorsten so he can integrated it to the wiki. Find attached the updated presentation & the bare-metal data in XLS format. Assignments for writing the Analysis: - Cloud-chapter: John - Data: Clara - IoT: Salvatore - Overall FI-WARE: Stefano - Methodologie: Thorsten - Open chapters: o Apps o Security (ask Pascal) o Use Case chapters (all of them not assigned) Any questions or corrections, please let me know /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Tue Oct 29 09:12:06 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 29 Oct 2013 08:12:06 +0000 Subject: [Fiware-wpl] test please ignore (and...good morning BTW) Message-ID: <393554EDCF801348BC53C7813C6CB73B1A682717@DEWDFEMB14A.global.corp.sap> Hi, Please ignore this test mail... Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Tue Oct 29 15:58:59 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 29 Oct 2013 14:58:59 +0000 Subject: [Fiware-wpl] [Fiware-testbed] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486067C00@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486060DDF@DEWDFEMB11A.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD66486067C00@DEWDFEMB11A.global.corp.sap> Message-ID: <393554EDCF801348BC53C7813C6CB73B1A682C8C@DEWDFEMB14A.global.corp.sap> Dear Thorsten, For WP3 chapter I plan to deliver tomorrow EOB (currently preparing the input and then sending around in WP3 chapter for approval). Best wishes Markus From: Sandfuchs, Thorsten Sent: Dienstag, 29. Oktober 2013 08:58 To: Leidig, Torsten; BISSON Pascal; Heller, Markus; daniel.gidoin at thalesgroup.com; ralli at tid.es; GLIKSON at il.ibm.com; sergg at tid.es; thierry.nagellen at orange.com Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu Subject: RE: [Fiware-testbed] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. Thanks to the cloud chapter which actually managed to contribute as planned. May I kindly ask what the other WPL/WPAs are envisioning for the final submission? Do you need more time or are you planning to not submit at all? Would you be in favor of shifting the deliverable deadline because of missing contributions and communicating this to the EC or do you think we should submit, even if a WP did not provide a contribution? Thanks for any comments. /Thorsten From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 24. Oktober 2013 09:26 To: Leidig, Torsten; BISSON Pascal; Heller, Markus; daniel.gidoin at thalesgroup.com; ralli at tid.es; GLIKSON at il.ibm.com; sergg at tid.es; thierry.nagellen at orange.com Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu Subject: [Fiware-testbed] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. Dear WPL & WPA colleagues (apps, cloud, data, iot, security), as planned below I would like to encourage and ask kindly for your contributions to the validation deliverable, which for your chapter the Testbed Team prepared as attached & in the testbed wiki. You will find the task for "your" chapter described in the doc - the section you have to fill is "Comments by WP leadership" for your chapter and should roughly cover answers to the questions, which I as well printed at the bottom of this email. These questions might help you find relevant and "interesting" things, the Reviews would like to know in relation to our "answer" to the validation of the use cases in phase 1. Please either directly change the DOC-file with "tracked"-changes - or contribute to the wiki where all pages from this deliverable are linked here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page#Structure_of_this_Document Please finish this task until Monday, 28.10. EOB the latest. If you have any questions, please don't hesitate to ask! Thanks a lot and best regards /Thorsten Questions to be answered by WPL/WPA * What went good, what went bad during this validation? * What was the recent actions implemented which address potential challenges identified during the validation? * Which challenges did you mainly identify, coming out of this validation? * What strength can you find for your chapter and how to further build upon this strength? * What measures did you take to mitigate the situation? * Overall acceptance over all validated GE for your chapter? (find answer Q.GE.11) * How deep have they been validated for your chapter? (find answer QGE.13) * Browse through the "scenario-based answers" (doc-files) and extract some relevant quotes good ones and bad ones, touching on your chapter GEs. - the doc files are linked here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Overview_FI-WARE_validation#Validation_of_non-functional_requirements * What would you do differently in the next validation round? * What would you find interesting from the use cases to better improve the validation? De : fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] De la part de Sandfuchs, Thorsten Envoy? : lundi 14 octobre 2013 10:25 ? : fiware-testbed at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-testbed] Minutes and action points on validation deliverable submission (10.5.2b) Dear colleagues, on Friday there was a testbed-internal session which discussed how to submit D.10.5.2b (the resubmission of the validation deliverable). We have a very tight schedule to submit this deliverable with all contributions in time. For this minutes I'm taking WPL/WPA on the CC list in order to let everybody know the status. Thorsten presented the approach and explained along the lines of the presentation what content should needs to be produced. - Mainly the testbed-team will in a neutral way write what we "see", judged by the numbers - things like: "SMARTAGRIFOOD rated the integration badly in the case of the XXX chapter...." We could try to come up with first assumptions on why these ratings did take place and dig deeper - but overall WPL/WPA need to do the _content_ driven analysis. "The reason for this was ..." or "We will take this serious and already implemented the following actions ..." Background are the graphs and tables prepared by Thorsten in the presentation and pivot-tables of the XLS. - Additionally and for the deliverable the "scenario based" questionnairs in DOC format need to be analyzed and "highs" and "lows" need to be extracted for the chapters. - Stefano wanted everybody to analyze the bare-metal XLS and try to come up with "new interesting" things somebody sees in the day. This task needs to be worked on in parallel within the week of 14.10. - 18.10. - everybody to report relevant findings on the 22.10. Rough time plan: KW42 (14.-18.10): main content work, Testbed-team writing what we "see", judged by the numbers KW43 (21.-25.10): finalizing text & hand-over to WPL/WPA team - 22th of October: deadline for the content work - goal: on 23th October WPL/WPA should be able to start their work with the content analysis (you will have ~3 business days) KW44 (28.-30.10): finalizing the DOC deliverable and starting a review cycle - Please volunteer if you want to be a reviewer for this deliverable KW44 (31.10): planned submission to EC Please - if possible - directly update the wiki : https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page#Structure_of_this_Document or the underlying pages. If unsure, just write the text in any other format and provide it ASAP to Thorsten so he can integrated it to the wiki. Find attached the updated presentation & the bare-metal data in XLS format. Assignments for writing the Analysis: - Cloud-chapter: John - Data: Clara - IoT: Salvatore - Overall FI-WARE: Stefano - Methodologie: Thorsten - Open chapters: o Apps o Security (ask Pascal) o Use Case chapters (all of them not assigned) Any questions or corrections, please let me know /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.bareno at atos.net Tue Oct 29 18:43:25 2013 From: juan.bareno at atos.net (=?UTF-8?B?SnVhbiBCYXJlw7FvIEd1ZXJlbmFiYXJyZW5h?=) Date: Tue, 29 Oct 2013 18:43:25 +0100 Subject: [Fiware-wpl] Open data: Unlocking innovation and performance with liquid information Message-ID: Dear Colleagues A new McKinsey report says that open data can help create $3 trillion a year of economic value across seven sectors. In a related podcast, the McKinsey Global Institute?s Michael Chui discusses the economic potential of open data and how governments and businesses can unlock it. more In summary, the use of open data: ?has a large potential economic value from its benefits, including increased efficiency, new products and services, and a consumer surplus (cost savings, convenience, better products) ?enhances big data?s impact by creating transparency, exposing variability, and enabling experimentation; helping companies to segment populations and thus to customize actions directed at them; replacing or supporting human decision making; and spurring innovative business models, products, and services ?creates multiple business opportunities, such as the potential to raise productivity, to improve new products and services, and to enable entirely novel lines of business for both established companies and entrants ?benefits consumers even more than businesses, by creating price and product transparency as well as new channels to provide feedback that improves the quality of goods and services (including public ones) ?entails business risks, including reputational issues related to the potential release of negative information; the potential consumer backlash from aggressive open-data use (for instance, in ads that target online consumers by following social-media activity); and the inadvertent release of confidential information, such as benchmarking data ?requires governments to play a central role by developing and implementing policies to mitigate consumer and business concerns about the misuse of open data and to help set standards that will allow the potential economic and social benefits to materialize ?faces barriers, including privacy concerns and the need for legal and regulatory frameworks Please find here attached the Executive Summary of the Mckinsey Report Br Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: Peter Stollenmayer [mailto:stollenmayer at eurescom.eu] Sent: jueves, 24 de octubre de 2013 9:43 To: Policy at fi-ppp.eu Subject: [FI-PPP Policy WG] For info: Public consultation on open research data Dear colleagues interested in open data (one of our nine priority items), The following was brought to me by KoWi, the EU Liaison Office of the German Research Organisations. I would like to share it with you for your information. The European Commission (EC) organized a one-day public consultation on open research data on July 2, 2013 in Brussels, which was attended by around 130 stakeholders from the research community, industry, libraries, publishers, funders and other institutions. The result of the consultation is summarized in the consultation report which was published on October 17, 2013. Based on the EC Communication ?Towards better access to scientific information? which sets out the open access policy objectives for the research funded by the Commission through Horizon 2020 the consultation will help the Commission to develop its policies on open research data. The discussion focused on the following five key questions: How can we define research data and what types of data should be open? When and how does openness need to be limited? How should the issue of data re-use be addressed? Where should research data be stored and made accessible? How can we enhance data awareness and a culture of sharing? Horizon 2020 will include a pilot on Open research data for specific topics in all three main parts of the programme which will ask participants funded in the respective projects to arrange for open access to the research data generated in their project. Further information: ? Public Consultation on Open Research Data ? Report of the European Commission Public Consultation on Open Access Research Data ? Information: 'Towards better access to scientific information? Beast regards Peter ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 339 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 4064 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 1116 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: MGI_Open_data_Executive_summary_Oct_2013.pdf Type: application/octet-stream Size: 4908823 bytes Desc: MGI_Open_data_Executive_summary_Oct_2013.pdf URL: From juan.bareno at atos.net Wed Oct 30 18:19:07 2013 From: juan.bareno at atos.net (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Wed, 30 Oct 2013 18:19:07 +0100 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Exploitation Message-ID: Dear Colleagues Please find enclosed the current version of the periodic report for your review. Each partner should fulfill its participation in each Task 1. 11.1 Market Analysis- nothing new since the last M24 Deliverable 2. 11.2 Exploitation- The Individual Confidential Exploitation Plans after the review and the ones requested for M30 and the Terms and Conditions fixing 3. 11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe the CONCORD meetings 4. 11.4 Standardization- Completed by Lindsay 5. 11.5 Community Building- Completed by Javier I miss more inputs on the 11.2 Exploitation plan regarding our new confidential exploitation plan and the fixing of Terms and conditions, as for example Thales and TI define I kindly ask the you to send me any feedback and/or comments no later than tomorrow, Thursday 31st, at 16:00 CET, thanks. Br Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: Juan Bare?o Guerenabarrena Sent: jueves, 17 de octubre de 2013 16:41 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); fiware-standardization at lists.fi-ware.eu; 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu) Cc: Nuria De-Lama Sanchez (nuria.delama at atos.net); Lindsay Frost (Lindsay.Frost at neclab.eu); Javier de Vicente (javier.devicente at futuranetworks.com); Miguel Carrillo (mcp at tid.es); JAVIER DE PEDRO SANCHEZ (jdps at tid.es) Subject: FW: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Dear Exploitation Colleagues 1. Progress report: request for contributions 2. Periodic Report M30 starts on May 2013 (M25) and ends on October 2013 (M30). 3. Each partner fulfill its participation in each Task a. 11.1 Market Analysis- nothing new since the last M24 Deliverable b. 11.2 Exploitation- The Individual Confidential Exploitation Plans after the review and the ones requested for M30 c. 11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe the CONCORD meetings d. 11.4 Standardization- Lindsay?? e. 11.5 Community Building- Javier?? 4. Deadline next Friday 25th October Thanks for your support Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: JAVIER DE PEDRO SANCHEZ [mailto:jdps at tid.es] Sent: martes, 15 de octubre de 2013 15:56 To: Juan Bare?o Guerenabarrena Cc: subsidies at tid.es Subject: RE: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Hola Juan Te remito la plantilla del WP11. Cada socio debe ser evaluado por a nivel de tarea. Por favor, conf?rmame que te ha llegado ?ste correo. Gracias mil. Salu2. Javier. De: subsidies-bounces at tid.es [mailto:subsidies-bounces at tid.es] En nombre de JAVIER DE PEDRO SANCHEZ Enviado el: martes, 15 de octubre de 2013 15:40 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: [Subsidies] FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 339 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 4064 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 45089 bytes Desc: image004.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D 1 2 5 - WP11 (3010).docx Type: application/octet-stream Size: 255903 bytes Desc: D 1 2 5 - WP11 (3010).docx URL: