[Fiware-ga] IMPORTANT AND URGENT: Second payment to beneficiaries incoporated to FI-WARE consortia through 3rd Open Call

JAVIER DE PEDRO SANCHEZ jdps at tid.es
Tue Mar 18 14:57:07 CET 2014


Dear all,

This e-mail is to inform you that, regarding the e-mail below, we have not received any objection from the consortia so far.
So, we are going to order the Second Interim Payment to the beneficiaries incorporated to FI-WARE consortia through 3rd Open Call as follows:

[cid:image001.jpg at 01CF42BA.018C5CC0]

Note: The accumulative payment cannot exceed the 85% of the overall funding per partner.

BR
    Javier.


De: JUAN JOSE HIERRO SUREDA
Enviado el: martes, 11 de marzo de 2014 11:42
Para: fiware at lists.fi-ware.eu<mailto:fiware at lists.fi-ware.eu>; 'fiware-administrative at lists.fi-ware.eu'; fiware-ga at lists.fi-ware.eu<mailto:fiware-ga at lists.fi-ware.eu>
CC: fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-pcc at lists.fi-ware.eu<mailto:fiware-pcc at lists.fi-ware.eu>; JAVIER DE PEDRO SANCHEZ; JUAN JOSE HIERRO SUREDA
Asunto: IMPORTANT AND URGENT: Second payment to beneficiaries incoporated to FI-WARE consortia through 3rd Open Call

Dear partners,

  We would like to proceed with a second payment to beneficiaries that joined the FI-WARE consortia as a result of their selection as a result of Open Call 3.

  Unfortunately, our payment formula setup in our Consortium Agreement didn't cover well the scenario where beneficiaries of an Open Call join after beginning of the last reporting period.   This was because it was (wrongly) assumed that beneficiaries of any Open Call would join before the end of the second reporting period.   As a result, following the formula established in the Consortium Agreement, beneficiaries of the Open Call 3 would only receive a first pre-financing payment at the beginning of the project and they would not get any additional payment before the very end of the project.

  This situation collocates these beneficiaries in a very odd and unfair situation compared to the rest of beneficiaries, who are getting paid as soon as the EC pays after each reporting period based on results of that period review so they have enough cash-flow to afford the activities of any period including the last period.

  On the other hand, we believe we should only proceed with a second payment to beneficiaries of Open Call 3 if there is evidence that their work so far will be accepted and consequently the declared costs will be likely accepted as well.  Because of that, we asked our Project Officer to provide us with an official email in which he may report on the status regarding acceptance of deliverables submitted by the new beneficiaries in Open Call 3 in month 29 (deliverables D11.5.1, D12.2.4 and D12.4.1).   Please find attached below the mail sent by our Project Officer anticipating acceptance of these deliverables.   This wasn't a surprise to us since we all know that beneficiaries of Open Call 3 are the ones dealing with branding, communication and dissemination activities and their performance so far can be very much positively evaluated.

  Based on the acceptance of these deliverables, we believe that we, as a consortia, are safe to proceed with a payment that covers the funding of declared costs from the date at which new beneficiaries joined the consortia and month 29, provided this doesn't exceed the 85% of the overall funding per partner, which is a rule that we must follow in all cases.

  Therefore, we will proceed with this payment unless we hear about any objection by any of the partners before Thursday March 13, 12:00pm.

  Please note that we cannot follow a similar approach with beneficiaries of Open Call 2 due to the fact that they didn't submit any deliverable for review in the last month 30 review.   Thus, the project officer could not send any message confirming acceptance of deliverables.   If we proceed to give a second payment to these other beneficiaries we would be incurring in risks since it may happen that their deliverables get rejected in the final review and such rejection may include some definite rejections.

  Don't hesitate to ask Javier de Pedro (in copy of this email) and myself any further questions you may have.   Again, I would like to stress the deadline for objection on Thursday March 13, 12:00pm.

  Best regards,

-- Juanjo Hierro


-------- Original Message --------
Subject:

FI-WARE: deliverables D11.5.1, D12.2.4 and D12.4.1

Date:

Fri, 28 Feb 2014 17:43:15 +0000

From:

<Arian.ZWEGERS at ec.europa.eu><mailto:Arian.ZWEGERS at ec.europa.eu>

To:

<raul.sanchez at futuranetworks.com><mailto:raul.sanchez at futuranetworks.com>, <jhierro at tid.es><mailto:jhierro at tid.es>

CC:

<subsidies at tid.es><mailto:subsidies at tid.es>, <CNECT-ICT-285248 at ec.europa.eu><mailto:CNECT-ICT-285248 at ec.europa.eu>


Dear Raul, Juanjo,
Just to let you know that I have just received the first review report draft.
In that draft, deliverables D11.5.1, D12.2.4 and D12.4.1 were accepted.
Probably, these deliverables will be accepted in the final review report as well. I have no reason to believe otherwise.
Best regards,
Arian.


________________________________

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-ga/attachments/20140318/0e94542b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29673 bytes
Desc: image001.jpg
URL: <https://lists.fiware.org/private/fiware-ga/attachments/20140318/0e94542b/attachment.jpg>


More information about the Fiware-ga mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy