Dear Juanjo, thanks for the updated figures. After a check of this new file, we see that this is not yet updated with the worked effort until M13. We kindly ask you to check two points for Consoft: · As we already told you in the previous e-mail, we have now real data and not anymore the estimated ones. In your calculations you used for Consoft an estimated value of the average PM cost of 4.781€, but the real value is 4.865€. · In your file is not yet considered the effort already worked in the period M11 – M13. The effort to be released should NOT include the one already worked until M13. If you grant us that you’ll address the two points above, we are available to insert a positive vote. BR Christian Da: fiware-bounces at lists.fiware.org [mailto:fiware-bounces at lists.fiware.org] Per conto di Juanjo Hierro Inviato: venerdì 16 ottobre 2015 08:39 A: fiware at lists.fiware.org; ficore-legal at lists.fi-ware.org; ficore-administrative at lists.fi-ware.org Oggetto: Re: [Fiware] FI-Core amendment: some adjustements regarding allocation of 3, 5% share of funding to QA testing activities Dear all, Please find enclosed the updates figures after fixing the issue mentioned yesterday and incorporating some feedback obtained during these last days: * summary text describing overall changes * final spreadsheet describing allocation of efforts/budget/funding Major changes are: * Changes to correctly calculate the funding deducted from the partners in the beginning of the project to reach the amount of 600 K€ to be devoted to QA testing. This was wrongly calculated previously based on funding assigned to all kind of RTD activities while it should have been calculated only to RTD activities linked to WP1.x and tasks 2.1.1, 2.1.2 and 2.1.3. As a result, some partners will be deducted a bit less while others a bit more. * Issues derived from wrongly assignment of effort/budget/funding to TCS rather than TS in task 1.7.2 * Breakdown per task of funding to be released in the case of TI and CONSOFT The rest of the DoW remains the same, although we will also incorporate some minor changes that some partners about little things to fix but it is worth capturing. We will also review carefully the description of the role of partners in each task to make sure content is consistent with the work done (or to be done). 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 On 15/10/15 12:47, Juanjo Hierro wrote: Dear all, Some partners identified a mistake we have made when we calculating the funding to be allocated for QA testing activities, associated to the decision we made in that respect at the very beginning of the project. I forward to you, the email that was sent at that moment (October 2014). As you can see, we explained that we were going to apply a cut in funding of activities under WP1.x and activities linked to development of FIWARE Ops tools. The cut in funding regarding development of FIWARE Ops tools should then apply to tasks 2.1.1, 2.1.2 and 2.1.3 and not 2.1.4. Unfortunately, we wrongly performed a cut in funding of task 2.1.4 as well as a cut in funding of the rest of RTD activities. We will fix this and will share with you an updated spreadsheet and summary text. This will mean that we may need to readjust the cut of funding that was applied to partners under WP1.x and tasks 2.1.1-3, in order to get the funding of QA testing activities as close to 600K€ as possible as expected. This should not mean a big change in the figures tough and since the formula to implement was clear since October 2014, we understand it won't mean any major issue. In the spreadsheet to be share we will also fix some issues that some of the partners did raise individually and we agreed were a mistake in the calculations that didn't affect others. 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/attachments/20151016/b60ecdc0/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy