Dear Colleagues I have not received any feedback on the WP11 deliverables nor your individual exploitation plans (except TID), although we settled the deadline last Monday 15th September Taking into account the new extension of the project until M44, as well as the WP11 deliverables, and aiming to gather into the individual exploitation plans all the events, commercial attempts and instances launched during this Q4, if any, we will move the final deadline to next 31st October. In the meantime, please not hesitate to send me your feedback regarding each Chapter´s ICT Market situation · We will make a follow-up in the next WPL meetings Thanks for your contribution Juan De: fiware-exploitation-bounces at lists.fi-ware.org<mailto:fiware-exploitation-bounces at lists.fi-ware.org> [mailto:fiware-exploitation-bounces at lists.fi-ware.org] En nombre de Bareno Guerenabarrena, Juan Enviado el: jueves, 24 de julio de 2014 12:31 Para: fiware-exploitation at lists.fi-ware.eu<mailto:fiware-exploitation at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-pcc at lists.fi-ware.eu<mailto:fiware-pcc at lists.fi-ware.eu> CC: MIGUEL CARRILLO PACHECO Asunto: [Fiware-exploitation] WP11 Tasks for partners related to deliverables in M41- Deadline 15th Sept Dear Colleagues I need your contributions to the final WP11 deliverables before the 15th September. What we expect mainly from you is the following: · Individual exploitation plans, following the instructions defined in recommendation 21 from the last review, see Annex 1- D11.2.3 attached and below- TID, IBM,FT, ENG, TI, THALES, INTEL, NEC, ATOS · All the individual exploitation plans should be described in the Annex 1 of the D11.2.3 · Although limited to the main issues requested from the commission, see Anne-1, you can also include and even improve the content provided in the last individual exploitation plan delivered, as SAP did. · Just additional/significative info that should be consider as confidential could be delivered in a confidential basis to Arian (Arian.ZWEGERS at ec.europa.eu<mailto:Arian.ZWEGERS at ec.europa.eu>) · We will make a follow-up in the next WPL meetings · D11.1.3- Market Analysis- Continue to analyze ICT Market situation in relation with each Chapter GEs · https://forge.fi-ware.org/docman/view.php/27/4551/D11.1.3-Market+and+Competition+Analysis+_M36v5.doc · Review each initial content per building block by WPL and Modify/Suggest/Add or provide reference documents to complete · Provide studies to prove the demand side in the main verticals identified, e.g. business related services and manufacturing · Provide documents related the policy and regulatory actions needed regarding the specific themes (Data protection, Cloud Computing, Security....) · D11.2.3- Exploitation Plan · https://forge.fi-ware.org/docman/view.php/27/4552/D11.2.3+Exploitation_Plan%2C_including_IPR_Managementv_M36+v3.doc · Review each initial content per building block by WPL and Modify/Suggest/Add what you consider regarding Business Capabilities, Positioning in the Market and Potential Usage Scenarios per technology · Please provide any feedback on the following- FI-LAB Modus Operandi, Financing and Business model definition is needed and even how this vehicle is to be created in the first instance is totally opaque and uncertain · How to create BUNDLES/PACKAGES- Any reference or documentation would be very helpful · The potential policy issues and impact on the specific exploitation activities of FI-WARE partners and the evolution of the FI LAB should be more specifically identified and described Thanks for your contribution Juan Recommendation 21: Provide credible and "real-life" exploitation planning In our opinion, all the industrial participants have the capabilities and funds necessary to propose a convincing exploitation plan, which should be at least commensurate with the public funds received. Each exploitation plan should include the following elements to facilitate implementation of the project results: a) At least one application where FI-WARE will be used, with the description of the architecture, the new functionalities enabled by the GEs, the way in which they will become part of the new application and its coding and how this is going to be synchronised with existing code and new applications being created. The organisation concerned should also identify which resources will be dedicated to this task, the "investment" reserved for this effort and its timeline. b) At least one client /client area should be identified, with the expected benefits for the client, the rationale that will be used to communicate / sell the new values to the clients, the expected pricing scheme (if any, otherwise declare that it will be offered for free) and the channels that will be used to achieve that goal, with the description of the internal incentives / motivations that will be activated to achieve the desired goal. c) At least one business partner for utilisation / dissemination should be identified, with the description of how that partner will participate in the co-development and/or co-distribution of the GEs. Timing and resources should be identified. d) A control mechanism for verifying adoption should be put in place and it should be described. e) One person with sufficient seniority in the organisation concerned should be identified as being responsible for the adoption and dissemination of FI-WARE, and it should be stated that that responsibility will stay for at least two years. This person should have the seniority commensurate with the responsibility, for example be responsible for a significant business unit. Those organizations that will be able to compile the above information would have engaged in the necessary internal processes and gone through sufficient internal debate and buy-in to give FI-WARE a realistic chance of success beyond the public financing. At a minimum all participants should meet their project responsibility to provide a decent implementation plan. The above should be dealt with in the forthcoming deliverable D11.2.3. Juan Bareño Research & Innovation Account Partner European Union Institutions-Iberia T. +34 912 148 859 M. +34 625 598 216 juan.bareno at atos.net<mailto:juan.bareno at atos.net> Albarracín, 25 28037 Madrid - Spain atos.net [cid:image002.png at 01CF21D2.D8BA98F0][cid:image003.jpg at 01CFD0CC.04816B50] ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20140916/a810818b/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4657 bytes Desc: image003.jpg URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20140916/a810818b/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy