Dear Juanjo, We just voted ‘No’ to the proposed amendment, knowing that it will, not change anything on the final results but at least to express that we don’t agree with some elements: * It was not planned to transfer funding to Thales Service and all WP1.7 activity for TCS was dedicated for Trustworthy Factory GE. To stop this GE could release a part of funding, planned for year 2. The description in “FI-Core - Budget - Amendment 1 - v35.xlsx” for TCS is totally different. * The part of funding for “Friendly testing” is now 5.32% (3.5% in the previous version …) was never discussed with all partners. Yes, you have sent an email in October 2014 but the percentage was never decided. Another point is that it is applied for all 25 months, but you should take into account that, for the new GEs stopped, only 13 months are due. * To propose directly funding figures without the real value depending on cost for Year 1 is risky. Normally, all efforts should be evaluated as PM and, after, to deduce the funding aspect. Overall, we can consider to stop our GE but, due to these errors, I have to vote “No”. Best regards Sebastien [@@THALES GROUP RESTRICTED@@] De : ficore-administrative-bounces at lists.fiware.org [mailto:ficore-administrative-bounces at lists.fiware.org] De la part de Juanjo Hierro Envoyé : vendredi 9 octobre 2015 13:16 À : fiware at lists.fiware.org; ficore-administrative at lists.fi-ware.org; ficore-legal at lists.fi-ware.org Objet : [Ficore-administrative] VERY IMPORTANT ON FI-Core AMENDMENT: General Assembly voting regarding FI-Core first amendment Dear partners, Thank you for your feedback and comments regarding the DoW drafts we have been exchanging these days. We also have final green light from the EC side to the proposed DoW. We have produced a very final version of the DoW you can download using the following link: https://www.dropbox.com/s/ga5wbrjo07duls3/FI-Core%20-%20DoW%20amendment%201%20-%2015-10-09%20v1.16.docx?dl=0 The attached spreadsheet summarizes the budget/effort/funding allocation among the partners as well as the details of the changes affecting each partner. You will see that the efforts (PMs) have been recalculated (both the PMs originally assigned as well as the ones to be left) based on the costs per PM reported by each partner in month 10, always maintaining the original and target budget and funding allocation. The PMs listed in the headers of the WP description forms within the DoW are aligned with the attached spreadsheet. The DoW incorporates a new version of the summary text describing the amendment. It mostly incorporates comments received from the EC associated to further engagement of companies that are part of the FIWARE Core Industry Group (e.g., creation of foundation or involvement in FIWARE marketing programme). PMs listed in the third table of that summary text also had to be recalculated in some cases following the approach described above. Now we have to proceed with a voting on the amendment. You should cast your vote in the following shared google docs spreadsheet: https://docs.google.com/spreadsheets/d/1u46iLP2TzkuPo5dZFFRHjqNjLNnGcZPlKo8muB-V1hQ/edit?usp=sharing Please note that the deadline to cast your vote is Friday October 16, 14:00 CET. We expect that the voting for this amendment will be positive. However, I believe that it is fair to share with you what we believe would be the consequences of a negative vote and the reaction by the EC (as they have anticipated during conversations maintained with them). The most probable scenario is that a formal declaration of "non-performance" would be declared on the project which would imply at least that: a) no further funding will be accepted/transferred to the partners by the EC until the non-performance status gets fixed (which would mean defining an implementing a plan which I can hardly believe is going to be different than the one defined through this amendment) b) work until month 13 would be carefully reviewed and assessed with all the risks this may imply regarding acceptance of costs during those periods of the project during which the service level provided, in terms of support of the FIWARE Lab or quality of documentation and support on individual GEris, has been far from excellence. With this info in advance, I believe you will be able to take a more informed decision. At the time we are writing this message, we are reviewing the description of partners' roles in each of the tasks to make sure there are no inconsistencies. However, this is mostly an editorial exercise which doesn't invalidate the results of the voting in place. In addition, there are two changes in the DoW that are pending but have zero effect in the activities of existing partners beyond the DoW draft now being circulated. We would like to introduce them if we have time before closing the NEF session where data about the amendment will be introduced: * Inclusion of iHub.eu as partner dealing with payments of bounties given away under the FIWARE bounty programme. Payment of bounties will become a hard administrative task (many payments of small amounts). Therefore, we are happy that this task can be taken by iHub.eu which is the new organization created to serve the FIWARE iHub network. They would get assigned the bounty programme budget in order to deal with those payments (currently assigned to TID until a beneficiary was identified). * Inclusion of Infotec and Tecnológico de Monterrey to declare activities where they are involved regarding the FIWARE community (setup and operation of the FIWARE Lab node in Mexico, contributions to work on Orion Context Broker, contribution to the FIWARE-ready IoT devices programme, support to activities linked to creation of a FIWARE community in Mexico). The funding of their activities would be provided by the Mexican government without meaning any transfer of funding from the EC, therefore affecting existing partners. The EC welcomes very much the inclusion of these two partners in the amendment if they manage to finalize their legal and financial validation process on time. Despite the effect of including these two new beneficiaries in this amendment is neutral to existing partners, we will carry out also a vote regarding their inclusion. For this reason, you will see there are two specific columns in the shared google docs where you are asked to cast your vote for this amendment. Best regards, -- Juanjo ______________________________________________________ Coordinator and Chief Architect, FIWARE platform CTO Industrial IoT, Telefónica email: juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com> twitter: @JuanjoHierro You can follow FIWARE at: website: http://www.fiware.org twitter: @FIWARE facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20151016/144b9ad6/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy