Which is the pin code, please?
Thanks
Clara Pezuela
Head of IT Market
Research and Innovation Group
ARI website<https://atos.net/en/insights-and-innovation/innovation-labs>
Atos Spain SA
Clara.pezuela at atos.net<mailto:Clara.pezuela at atos.net>
+34 675 62 9974
[Atos_Olympic_Games_Logo_signature]
From: Federico Michele Facca [mailto:federico.facca at martel-innovate.com]
Sent: Wednesday, November 02, 2016 2:02 PM
To: De Lama Sanchez, Nuria
Cc: Stefano De Panfilis; Pierre Yves Danet; Pezuela Robles, Clara M; Muryshkin, Peter; Ahle, Ulrich; Paolo Fabriani; Fiware-sustainability-proposal at lists.fiware.org; Piero Corte; Carmen Mac Williams; elke.rupp at zv.fraunhofer.de
Subject: Re: [Fiware-sustainability-proposal] fi-next gap finalisation
Hi Nuria,
I think - if I recall the discussion at proposal time - that the difference will be in the fact that today FIWARE Lab provide limited resource for free,
and tomorrow beside that will have a pricing schema for users that wants more than few vms and/or for more than 9 months.
Btw, for achieve this it is probably important to check with NRENs if this is actually possible :) or change the network backbone for nodes where
paying users will be hosted.
Best,
Federico
Dr. Federico Michele Facca
Head of Martel Lab
Martel Innovate
Dorfstrasse 73 - 3073 Gümligen (Switzerland)
0041 78 807 58 38
0041 31 994 25 25
martel-innovate.com<http://martel-innovate.com>
On 02 Nov 2016, at 13:48, De Lama Sanchez, Nuria <nuria.delama at atos.net<mailto:nuria.delama at atos.net>> wrote:
Do we have the names of all these projects?
Have they been informed somehow of the fact that they will have to pay to use FIWARE Lab? This is important, since we stated in many events that the infrastructure, just for experimentation purposes, was for free. They have probably designed their budgets having this in mind. If they did not assign a budget for this at the proposal/negotiation stage, they will be unable to pay for it at least in the context of the project.
As a result, I think an analysis of this should be made before deciding the approach. Instead, a combined model could be offered based on a minimum set of resources provided for free and a value proposition that increases resources and services based on fees. Of course this “offering” should be designed and communicated to them so that they can take their decisions.
I think it is dangerous coming to them at some point in time stating they have to pay unless this is done before they commit to use FIWARE. However, if they get clear information on the offering and prices early enough, then it would make sense to me. The other way would damage the credibility of FIWARE.
My two cents.
<image001.png>
Nuria de Lama
Research & Innovation
European Programs Manager
Vice-Secretary General Big Data Value Association
M +34 680645692
T +34 91214 9321
F +34 91754 3252
nuria.delama at atos.net<mailto:nuria.delama at atos.net>
Albarracín 25
28037 Madrid
Spain
www.atosresearch.eu<http://www.atosresearch.eu/>
es.atos.net<http://es.atos.net/>
<image002.png>
Feel free to download our booklet at
http://booklet.atosresearch.eu/
From: fiware-sustainability-proposal-bounces at lists.fiware.org<mailto:fiware-sustainability-proposal-bounces at lists.fiware.org> [mailto:fiware-sustainability-proposal-bounces at lists.fiware.org] On Behalf Of stefano de panfilis
Sent: Wednesday, November 02, 2016 12:34 PM
To: Pierre-Yves Danet; Pezuela Robles, Clara M
Cc: Muryshkin, Peter; Piero Corte; Fiware-sustainability-proposal at lists.fiware.org<mailto:Fiware-sustainability-proposal at lists.fiware.org>; Ahle, Ulrich; Paolo Fabriani; Carmen Mac Williams; elke.rupp at zv.fraunhofer.de<mailto:elke.rupp at zv.fraunhofer.de>
Subject: Re: [Fiware-sustainability-proposal] fi-next gap finalisation
dear pierre-yves and clara,
as said in other emails, we well know, that the cuts to fiware lab operations will not allow the full support till the end of the project. we do expect as you well pointed out that atos, engineering and image lab/orange will exhauste their resources for this task at the end of 2017.
on the other hand, we do expect also that some of the 200 eu funded projects, under the the various ict call, which said they will use fiware lab they will. we agreed with the ec that we are in the position, and rigth, to charge them.
we will have some months, not many but for sure within june 2017, to sort out all the questions pierre-yves nicely listed, which of course are the same questions i do have in mind.
happy to talk about all of that and more during this afternoon call.
@pierre-yves: nice to have your bridge. can you send a calendar invitation to all? or shall i? thank you in advance
ciao,
stefano
2016-11-02 11:21 GMT+01:00 <pierreyves.danet at orange.com<mailto:pierreyves.danet at orange.com>>:
Dear Stefano,
Looking to your proposal, I understand that the real reason of this new budget is directly linked with the new FF man power costs which double comparing to what we put in the initial proposal.
Now regarding Orange, we need some more time to evaluate the real impact of our contribution on WP3 but also together with Images&Réseaux which will operate the Lannion FIWARE Lab. You may know that such a sand box needs public funding to be sustainable and the 30 initial MM were already really short. Now with 16 MM, we can operate the node until end of 2017, not more.
You say that in 2018, the operation of the FIWARE labs will be paid by the 200 EC projects using the FIWARE technology but how it will work ?
o What will be the entry point to collect the fees ? The foundation ?
o How the repartition of the fees will be managed ? All the project will request a FIWARE-Lab account and the foundation will distribute among all the FIWARE-Lab
o Or if not, at the end the FIWARE-Lab will enter in competition and only the FIWARE-Lab hosting an App will get fees ?
So I shall participate to the call this afternoon and I can offer a bridge if needed (see attached calling numbers, PIN = 158990425) but I shall not be able to give our final position.
Thanks for clarification
PY
De : fiware-sustainability-proposal-bounces at lists.fiware.org<mailto:fiware-sustainability-proposal-bounces at lists.fiware.org> [mailto:fiware-sustainability-proposal-bounces at lists.fiware.org<mailto:fiware-sustainability-proposal-bounces at lists.fiware.org>] De la part de stefano de panfilis
Envoyé : lundi 31 octobre 2016 22:40
À : Fiware-sustainability-proposal at lists.fiware.org<mailto:Fiware-sustainability-proposal at lists.fiware.org>; elke.rupp at zv.fraunhofer.de<mailto:elke.rupp at zv.fraunhofer.de>; Muryshkin, Peter; Carmen Mac Williams; Piero Corte; Paolo Fabriani
Cc : Ahle, Ulrich
Objet : Re: [Fiware-sustainability-proposal] fi-next gap finalisation
dear all,
as promised, please find attached the new budget built according to the esr the ec sent.
major changes are:
1. we cut of about the 80% the funding to fiware-lab operations. the idea is that starting from 2018 we are going to charge the services of fiware lab to ec funded projects who based their prtoposal on the use of fiware technologies and fiware lab. so we do expect to keep the same level of operations as at this point in time 200 new projects wrote in their doa such use.
in the wp4 only the task 4.3 is affected
2. we reduced a bit the effort in wp 3. please note that the ec strongly pushed during bilateral conversation to keep this to a much more less level. we succeded not to have that, still a limited cut was done here (a total of about 150k). only for create-net we took few months in fiware ops.
3. a new task 2.5 have been created to support the activity of the community manager. actually this was re-described as the implementation of the devrel programme.
4. a new task 5.1 (the existing conveniently renamed 5.2 and 5.3) in order to support the go-to-market strategy.
all the changes described are in red in the new sheet "doa effort and figures - v2.0".
of course many of you recognise that martel, shaw, infotec and itesm have not affected by the above described changes. this is due to the fact that their budget is not in charge to the ec and thus to the level of funding of the project.
the confcall this wednesday will on powwownow with pin 436393, of course unless any of you has a different confcall bridge to offer. at the ff we are setting up our services so for next calls we will have gotomeeting at our disposal.
in addition please find attached the ff bylaws as accepted by the charlottenburg court in berlin. so yes we are now registered :-)
ciao,
stefano
2016-10-28 8:18 GMT+02:00 stefano de panfilis <stefano.depanfilis at eng.it<mailto:stefano.depanfilis at eng.it>>:
dear all,
apologises for this long silent phase, but the work to register the ff (fiware foundation) took most of our energies, the good news is that most likely today we had the formal registration at the charlottenburg court here in berlin.
consequently to that we have to finalise quickly the gap which includes a revised version of the doa.
changes as i wrote you are in agreement with the esr, but in some cases are quite intense. following all of that i suggest to have a confcall (if you disagree on the proposal of the new budget) on this coming wednesday at 14:30.
the new budget sharing will come in a moment.
there is still a point i'd like to share with you.
the ec, in the case of the validation of the fiware foundation by their services takes too long, is asking to engineering (only becouse i'm the acting coordinator) to take over the coordination role having the ff as its subcontractor. since anyway such validation will terminate along this year, the agreement is that we have a very quick and prompt amendment within 2016 putting everything as in its normal state, i.e. the ff as coordinator.
if this is the situation then the commencement date can be this 1st november as the contract signature migth be within november. if the ec accepts to delay till the ff is validated by their services, then most likely the commencemnt date is 1st december.
both case the ec would like to use the rule that the commencement date is the first day of the month where the contract signature occurs. they said to me yesterday, if you wish to start this 1st november, as you know, you start at your own risk.
btw, this morning i'm going to have another, final (?), call with the ec to take the final decision.
in addition, we at ff take this project extremely seriously as it to be the cornerstone of the ff boost and start-up phase and the founders of the ff as well being all of them platinum members of the ff (from the attached fee code you see that is comparable with the funding those partners will receive by the ec in fi-next).
to the attached email i received only one answer (martel consulting) which is a positive sign if i have to take it in the silence=agreement model, but it is that?
please find attached for your convenience the fee code for joining the ff which we see as a (strong)requisite to be in the fi-next project. this point have been shared with the ec.
stay tuned as in a couple of hours you'll get the new budget and the request for the missing bits of documents.
ciao,
stefano
2016-09-23 13:14 GMT+02:00 stefano de panfilis <stefano.depanfilis at eng.it<mailto:stefano.depanfilis at eng.it>>:
dear all,
as you migth know on last 13 september we have signed the fiware foundation bylaws in front of the notary for submission to the german authority for registration.
till today we did not yet received the ok, but we are rather confident things will be finalised within this week or early next week at most.
in this context now the fiware foundation can properly take over the coordination of the fi-next project starting from its contractual finalisation.
due to my role of chief operation officers at the fiware foundation i'm now in charge of such a task with the help of the team at telefonica.
with this email i'd like to make you all aware about the evolution of the work we are already doing.
1. the ec is completely aware of all the steps we are making and are quite helpfull in the all contractual fianlisation matters
2. following the esr we all received we are reviewing the proposal text in order to have it best fitting as the project doa ("description of action", new name for "description of work" - dow).
3. friday last week we (ulrich, juanjo and myself) had a conversation with the ec. they highligthed that:
3.1 the doa must follow the recommendations in the esr
3.2 it is essential to provide more resources to the fiware os community building and evangelisation
3.3 the technical activities themselves should be effectively focussed on few aspects and in particular to strengthen the iot ready initiative we have already launched in fiware. this last point is not in the esr, but was strongly mentioned during the meeting.
we are now elaborating a new budget share with as much as possible minimal impact. of course we will distribute it to you all before it to be submitted to the ec. anyway it is clear that in order to strengthen the project, and the position of all beneficiaries in the project, it is highly recommended, if not mandatory, that each partner in this consortium shows a real committment to fiware and its long term sustainability. the only way to do so is that each partner in the consortium joins the fiware foundation.
to this extent to this email you'll find attached the fiware foundation bylaws in the version we signed and submitted to the german authorities.
the fees, still under finalisation by the fiware foundation board of directors, are as follows:
- platinum members 200.000 eur per year plus 2 fte
- gold members 0.025 of the annual turnover
- associate members flat rate to be fixed (this category however applies only for academia and research institutes)
- individual members free of charge (this category applies only physical persons, this is anyhow mandatory for the persons in the consortium, as well outside fi-next, which will actively contribute with assets, e.g. code, documentation, courses, tests, etc).
the plan is finalise everything by next week.
in a next email i'll come with the exact duties for each of all with respect to the contractual documentation such as declaration of honour and the like.
in the meanwhile, please let me know if you have serious objections in joining as member the fiware foundation.
ciao,
stefano
--
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy
tel (direct): +39-06-8759-4253<tel:%2B39-06-8759-4253>
tel (secr.): +39-068307-4513<tel:%2B39-068307-4513>
fax: +39-068307-4200<tel:%2B39-068307-4200>
cell: +39-335-7542-567
skype: depa01
twitter: @depa01
--
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy
tel (direct): +39-06-8759-4253<tel:%2B39-06-8759-4253>
tel (secr.): +39-068307-4513<tel:%2B39-068307-4513>
fax: +39-068307-4200<tel:%2B39-068307-4200>
cell: +39-335-7542-567
skype: depa01
twitter: @depa01
--
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy
tel (direct): +39-06-8759-4253<tel:%2B39-06-8759-4253>
tel (secr.): +39-068307-4513<tel:%2B39-068307-4513>
fax: +39-068307-4200<tel:%2B39-068307-4200>
cell: +39-335-7542-567
skype: depa01
twitter: @depa01
_________________________________________________________________________________________________________________________
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-06-8759-4253
tel (secr.): +39-068307-4513
fax: +39-068307-4200
cell: +39-335-7542-567
skype: depa01
twitter: @depa01
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. _______________________________________________
Fiware-sustainability-proposal mailing list
Fiware-sustainability-proposal at lists.fiware.org<mailto:Fiware-sustainability-proposal at lists.fiware.org>
https://lists.fiware.org/listinfo/fiware-sustainability-proposal
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-sustainability-proposal/attachments/20161102/4864672c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11614 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/fiware-sustainability-proposal/attachments/20161102/4864672c/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy