FYI. Creo que en este mail de respuesta a SAP resumo como debemos tratar el asunto de la finalización del proyecto FI-WARE actual o el arranque del nuevo proyecto FI-Core: el público general debe ignorar por completo la existencia de proyectos detrás del programa. Nuestros mensajes de comunicación giran en torno a productos/servicios (FI-WARE, FI-Ops, FI-Lab) no en torno a proyectos.
Copio a toda la lista de fiware-comms para que estemos todos sincronizados ...
Saludos,
-- Juanjo
-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto: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: FW: Communication Plan for the planned Extension of FI-WARE-1 for M36-leaving partners and M40-staying partners
Date: Mon, 14 Apr 2014 18:47:02 +0200
From: Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>
To: Heller, Markus <markus.heller at sap.com><mailto:markus.heller at sap.com>, Miguel Carrillo <mcp at tid.es><mailto:mcp at tid.es>
CC: FI-WARE WPA (fiware-wpa at lists.fi-ware.org<mailto:fiware-wpa at lists.fi-ware.org>) <fiware-wpa at lists.fi-ware.org><mailto:fiware-wpa at lists.fi-ware.org>, FI-WARE WPL (fiware-wpl at lists.fi-ware.org<mailto:fiware-wpl at lists.fi-ware.org>) <fiware-wpl at lists.fi-ware.org><mailto:fiware-wpl at lists.fi-ware.org>
Dear Markus,
FI-WARE is technology that is there to stay, no matter if some project that was covering some activities related to FI-WARE ends (despite that project happens to be named as FI-WARE) or some partners decide to no longer be involved.
Our target audience cares about the technology and its sustainability, whether there will be a commercial offering around FI-WARE, how vigourous the public-private partnership behind is, etc. They don't care about projects. Indeed we have always insisted in all our events since almost one year that a genuine aspect of the FI-PPP program is that we are not following a project-oriented approach (as in regular FP7 activities) but a product-oriented approach. On the other hand, nobody has came to me asking when this or that project end but asking questions such as "Are Telefónica or Orange (to just mention the name of two partners) committing to support this commercially?". Those are the questions that matter to our target audience and we don't want them to be distracted by other questions which shouldn't affect them.
We won't announce, for example, that a new project (FI-Core) will start taking over activities of the previous. FI-Core may start and end, but this is not the plan for FI-WARE, FI-Ops and FI-Lab. Users won't experience any difference in the operations of FI-Lab while we will transition between the FI-WARE project (I insist, the project) and FI-Core. Why should I mention it to them then ?
Just for your info, we will explicitly avoid to talk about FI-Core in future communications. We want that the existence of FI-Core becomes transparent to the Community. We will only communicate about FI-WARE, FI-Ops and FI-Lab.
In line with all the above, public statements about ending the FI-WARE project (which would create confusion without no value) or starting FI-Core won't be made.
If SAP plans to make any public statement on your own, it would be nice to know and we request to be able to review it as to make sure that you don't bring wrong messages.
Best regards,
-- Juanjo
-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto: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/04/14 15:41, Heller, Markus wrote:
Hi Juanjo,
Pinging this topic again about public communication about the extension.... I think we made a note on this somewhere in the WPL/WPA minutes but would like to ask for a current update on this:
Can we ask Ogilvy or so to issue such public statements about the extension period to prepare the public a bit beforehand that the FI-WARE projects goes on while some partners leave?
Maybe you have already communicates something somewhere publicly? Could you please point me to something?
Best
Markus
From: Heller, Markus
Sent: Montag, 31. März 2014 14:51
To: FI-WARE WPL (fiware-wpl at lists.fi-ware.org<mailto:fiware-wpl at lists.fi-ware.org>); FI-WARE WPA (fiware-wpa at lists.fi-ware.org<mailto:fiware-wpa at lists.fi-ware.org>)
Subject: Communication Plan for the planned Extension of FI-WARE-1 for M36-leaving partners and M40-staying partners
Hi Juanjo, all,
Some of us are leaving at the originally planned project end for FI-WARE-1. The consortium falls then into a group leaving in M36 and another group extending until M40 which may need explanation to stakeholders.
The extension of the project will not go unnoticed and may cause confusion ("have they failed and need more time...") and may cause some bad image in the public and shade bad light on EC maybe as well for organization / cost management.
in M36, while others have chosen to go into an extension period on their own decision. For example, it must be ensured that public can get a positive opinion about this extension (cost neutral...) and that leaving partners are not seen negatively because of leaving at M36, and other way round it must be ensured that longer staying partners are not seen negatively for staying longer. For both we must transmit that the different end dates are not a failure or such but a planned approach towards the projects success either for M36 and M40.
I am sure that we are currently already talking about the extension of FI-WARE-1 in the dissemination activities/events, but I have not seen any written communication on this - as it is only in planning with DOW amendment 6 currently, of course.
But after the dow amendment 6 is signed, the extension is in force. But we do not need to wait until then to have the communication for this ready.
As I am not fully aware of the current communication plan for announcing the extension, so I would like to ask for an update here:
I guess, you are planning for this. Nevertheless to be sure on this, I would like to propose an official communication to happen on our usual channels (e.g. on blogs, website, press, etc. stating some core messages to position the extension with a positive perception in the public on our own initiative.
- FI-WARE-1 project was planned in 2010 or so originally to run until M36. Impressive results so far reached until M36 like X, Y,Z. Results can be seen by anyone (FI-lab, GEs open source, ....)
- With the end of FI-WARE-1 nearing
o Some partners are leaving after having fulfilled their commitments and with considerable results (e.g. in GEs, in use cases, in backlogs, in fi-lab, ...) "with success and as planned".
o Some would like to go on after M40. Reasons are: X, y, outreach, prepare the activities of such partners who are in FI-WARE-1 and will become members of FII-WARE-2
- EC is satisfied with both decisions by partners.
- Important? Cost-wise EC / Tax payer: Extension is cost-neutral so tax-payer does not pay extra....(optional?)
- Having some partners leave and some partners stay is the consortiums approach to either fulfill the project goals with results until the original end of M36 and giving the ability for partners who additionally want to go beyond.
- We should mention some exemplary success examples of the whole team that acted until M36 (FI-LAB, branding, results, catalog, GE collection impressive,...)
- We should mention the new plans for extension period as stated for EC (using new opportunities that have become possible during project, dissemination more than expected, further outreach, ...
- We can explain in a sentence how is work planned between FI-WARE-1 and Fi-WARE-2? Handover is perfectly planned and e.g. use cases and third parties will never be let alone...
- Other messages....
Important: Can we be supported here by High key personnel (EC) for such announcement. For example, who can communicate on this extension to support a positive image here. I remind us for the blog article where even prominent EC members (Mario Campolargo?) answered as a reaction to a critical blog and in this extension case maybe we can plan for a prominent supporter upfront that could explain the extension to the public if needed?
What are our current plans on such communication, when and how do we want to rollout the extension? Afterall the extension is beyond the original project and any uncommented extension may be perceived negative / as a delay for delivery in the public or in our stakeholders views.
What is the planned timeline for this? When is the first announcement going to happen? How can e.g. Ogilvy support such activity to publish our own statement for the extension that will happen.
Again, I guess you already plan for this, can you please update us on this topic?
Best wishes
Markus
________________________________
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: <https://lists.fiware.org/private/fiware-comms/attachments/20140414/40fabad1/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy