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<https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2> //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<mailto:fiware-exploitation at lists.fi-ware.eu>; fiware-standardization at lists.fi-ware.eu<mailto:fiware-standardization at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>
Cc: nuria.delama at atos.net<mailto:nuria.delama at atos.net>; Lindsay Frost; javier.devicente at futuranetworks.com<mailto:javier.devicente at futuranetworks.com>; mcp at tid.es<mailto:mcp at tid.es>; jdps at tid.es<mailto: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<mailto:juan.bareno at atos.net>
www.atos.net<http://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<mailto: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<mailto: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> [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<mailto:fiware-wpl at lists.fi-ware.eu>'
CC: subsidies at tid.es<mailto: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<mailto: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<mailto: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: <https://lists.fiware.org/private/fiware-standardization/attachments/20131021/9150d9bd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 339 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/fiware-standardization/attachments/20131021/9150d9bd/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 4064 bytes
Desc: image002.gif
URL: <https://lists.fiware.org/private/fiware-standardization/attachments/20131021/9150d9bd/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 45089 bytes
Desc: image003.jpg
URL: <https://lists.fiware.org/private/fiware-standardization/attachments/20131021/9150d9bd/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy