[Fiware-sustainability-proposal] fi-next gap finalisation

[pierreyves.danet at orange.com]

Dear Stefano, all,

We are making a common answer to your proposal together with Images&Réseaux due to the fact that we are working on the same FIWARE Lab (Lannion node).
This answer is a consensus between Image&Reseaux (that operates the FIWARE Lab hosted in Lannion) and Orange.

First, we would like to say that we are very surprised with the procedure because Horizon 2020 rules does not allow any negotiation and modification between the proposal and the DOA and we understand that a lot of changes occurred (coordinator, budget, tasks, …) which seems to be not very fair regarding the proposals that have been rejected on the same call.

In case it is a strong recommendation from the EC to move that way, regarding the impact of the new budget on Lannion node (even we are quite reluctant of these changes because we have planned to operate this node until end of 2018 with FI-NEXT funding), in this new budget we can only commit to operate it until end 2017. In addition, we do not understand why some nodes get 20 m*m and ours only 16 m*m, for us it is the same amount of work to operate a node wherever it is located, so please make the alignment.

We are really committed to ensure Lannion node sustainability and we are hardly working with the Brittany region in order to secure it, it is why we ask you (as decided during our last call) to add a new deliverable with a deadline in June 2017 proposing Business plan scenarios and not only the one based on EC project contributions because we don’t believe it is the most relevant one (we don’t understand how we can ask money from some users as for others it will be for free). This deliverable has to answer at least the following questions :

·         What is the entry valuable services that partners are agree to pay for ? - Models of users and models of platforms/services-  How the FIWARE Lab platforms have to evolve to reach such an objective ? etc.

·         What will be the entry point to collect the fees from EC projects ? The foundation ? If yes, please make it transparent..

·         How the allocation and dispatching of fees will be managed ? Do all projects will request for a FIWARE-Lab account ? and will the foundation plan to distribute among all the FIWARE-Lab ?

·         Or if not, at the end the FIWARE-Lab will enter in competition and only the FIWARE-Lab hosting an App will get fees ?

Finally, we would like to insist on the huge importance to maintain free access to the nodes for not only European developers but also for worldwide developers.  It is a question of easy use and availability that is essential to expand the FIWARE community and it is key to propose a similar SLA on all nodes in order to ensure a balance use of each node.

We hope that you understand our position, please do not hesitate to react we will be happy to debate or clarify.

Kind regards

PY DANET
G MAUGIS
J RIGA


De : 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; 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 (secr.): +39-068307-4513
fax: +39-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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-sustainability-proposal/attachments/20161107/7fb6f67c/attachment.html>