Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-1795

FIWARE.Request.General. trouble obtaining a PIC

    Details

      Description

      Hi there,

      I’m trying to submit a proposal, but cannot figure out how to obtain the PIC number. I’ve done as stated in the application and registered for the ECAS account and I have that now, but from there there’s no way to get the PIC number.. that I can see anyway… These are the directions I’ve been following: http://ec.europa.eu/research/participants/portal/doc/call/fp7/fp7-ict-2013-10/33018-obtaining_pic_and_ecas_en.pdf <http://ec.europa.eu/research/participants/portal/doc/call/fp7/fp7-ict-2013-10/33018-obtaining_pic_and_ecas_en.pdf>

      Kind regards,
      ileana
      _______________________________________________
      Fiware-general-help mailing list
      Fiware-general-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-general-help

      [Created via e-mail received from: Ileana Sondergaard <ileana.sondergaard@gmail.com>]

        Activity

        Hide
        pablo honrubia Pablo Honrubia added a comment -

        Dear Ileana,

        Thanks for your email. If you are thinking in applying to the Fiware
        Acceleration Program there is no need for you to ask for a PIC. These open
        calls, even within FP7, are NOT managed directly by the EC but by 16
        entities called Accelerators. You can find all the details and contact
        information at www.fiware.org.
        On the other hand if you are intending to apply to a standard Open Call
        from the EC under the H2020 program (FP7 is already over since 2013), then
        you will need a PIC, but any support on that should come from the EC
        directly. Fiware has nothing to do with the process.

        Hope this helps,
        Pablo Honrubia
        Head of the Fiware Press Office.
        El 26/12/2014 16:11, "Ileana Sondergaard" <ileana.sondergaard@gmail.com>

        Privileged/Confidential Information may be contained in this message. If
        you are not the addressee indicated in this message, you should destroy
        this message. For more information on WPP's business ethical standards
        and corporate responsibility policies, please refer to WPP's website.

        _______________________________________________
        Fiware-general-help mailing list
        Fiware-general-help@lists.fi-ware.org
        https://lists.fi-ware.org/listinfo/fiware-general-help

        Show
        pablo honrubia Pablo Honrubia added a comment - Dear Ileana, Thanks for your email. If you are thinking in applying to the Fiware Acceleration Program there is no need for you to ask for a PIC. These open calls, even within FP7, are NOT managed directly by the EC but by 16 entities called Accelerators. You can find all the details and contact information at www.fiware.org. On the other hand if you are intending to apply to a standard Open Call from the EC under the H2020 program (FP7 is already over since 2013), then you will need a PIC, but any support on that should come from the EC directly. Fiware has nothing to do with the process. Hope this helps, Pablo Honrubia Head of the Fiware Press Office. El 26/12/2014 16:11, "Ileana Sondergaard" <ileana.sondergaard@gmail.com> – Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message, you should destroy this message. For more information on WPP's business ethical standards and corporate responsibility policies, please refer to WPP's website. _______________________________________________ Fiware-general-help mailing list Fiware-general-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-general-help

          People

          • Assignee:
            pablo honrubia Pablo Honrubia
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: