[cloud-marketplace-proposal] Template for the allocation of PMs by partners playing the role of IaaS Cloud, Platform Cloud or Independent Marketplace providers willing to integrate their markeplaces with ECM

Juanjo Hierro juanjose.hierro at fiware.org
Thu Feb 17 19:26:23 CET 2022


Dear all,

   Please find enclosed a template that partners playing the role of 
IaaS Cloud, Platform Cloud or Independent Marketplace providers willing 
to integrate their markeplaces with the European Cloud Marketplace may 
take as reference for the allocation of PMs to the different tasks in WPs.

   Of course, final budget (therefore funding) will vary from one 
partner to the other because the direct personnel costs per person*month 
would be different.  In the provided template, we are taking an 
hypothetical partner named "Acme" whose average direct costs per 
person*month would be 7000€.  In your particular case, could be the 
same, higher or lower.

   Now, the rationale that I hope will allow you to understand the 
assignment and may help you to assess how well this reference allocation 
works for you.

   Partners of this profile like you are expected to participate in the 
following tasks:

  * Task 3.6, as you have to work towards integrating their marketplaces
    with the ECM using the integration APIs the ECM will provide:
      o Such integration will take place during the 6 months that happen
        right after delivery of first version and second version of the
        ECM planned in month 12 and 24 (see target gantt), therefore 12
        months net.
      o we propose a team of 4 people working in such integration full
        time during those 6 months:
          + one working in the integration of the backend of your
            marketplace with APIs exported by the ECM
          + one working in the integration with the Distributed Identity
            and Access Management framework proposed in ECM (based on
            standards like OpenID Connect and VC/VP)
          + one working in other possible adaptations of required as a
            result of the integration with the ECM
          + one testing/validating
  * Task 4.5 - Training:
      o The team referred above will receive training the month before
        each version of the ECM is released
      o Since there are 4 people in the team and 3 training months, you
        have 12 PMs
  * Task 4.1 - Initial roll-out
      o Once the integration (carried out in task 3.6) is finished,
        there is 6 months of roll-out of your marketplace integrated
        with the ECM
      o Since there are two roll-outs planned during the project, this
        task matches 12 months net
      o We propose that a team of 4 people is focused in the success of
        the roll-out during the period.  They may be the same that
        performed the integration but not necessarily
  * Tasks 2.4, 5.1 and 5.2:
      o We essentially propose one person fully devoted to:
          + bring requirements that need to be taken into consideration
            during initial definition and roadmap of the product (12 PMs
            in task 2.4)
          + participate in discussions regarding governance structure
            (12 PMs in task 5.1)
          + participate in discussions regarding definition of
            revenue-based model (12 PMs in task 5.2)
  * Task 2.1, marketing activities
      o We expect that you get engaged in dissemination activities
        (social networks, involvement in events, etc).
      o We expect this will mean 50% of one FTE (can be one person 50%
        of his/her time or 2 people, one for social media, another for
        other matters, 25% of their time, for example)

   In addition, we propose 30 K€ in travels.

   Notes:

  * Partners that are collaborating around a specific IaaS Cloud
    offering or platform offering (e.g., Portel and IDOM regarding Smart
    Ports) will have to split this allocation of resources.
  * There are partners that will assume additional roles beyond that of
    a partner only interested in integrating their marketplace with the
    ECM.  They will have to propose additional PMs in other tasks.  The
    above schema works regarding PMs to allocate for fulfilling the role
    of IaaS Cloud / Platform Cloud provider.  A given partner may assume
    additional roles

   Hope it helps.  Please re-send your budget estimation based on this 
to Alberto and me (we may accept some adjustments) or simply confirm to 
us by mail that the mentioned schema works for you.

   If you have any question about the above, please come back to us.

   Cheers,

-- 
Document
Juanjo Hierro
Chief Technology Officer
juanjose.hierro at fiware.org
www.linkedin.com/in/jhierro <https://www.linkedin.com/in/jhierro>
Twitter: @fiware <https://twitter.com/fiware> @JuanjoHierro 
<https://twitter.com/JuanjoHierro>








-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/cloud-marketplace-proposal/attachments/20220217/4dece0ba/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foundation-logo.png
Type: image/png
Size: 8201 bytes
Desc: not available
URL: <https://lists.fiware.org/private/cloud-marketplace-proposal/attachments/20220217/4dece0ba/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Budget and efforts V0 - template for IaaS or Platform cloud providers.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 479875 bytes
Desc: not available
URL: <https://lists.fiware.org/private/cloud-marketplace-proposal/attachments/20220217/4dece0ba/attachment-0001.xlsx>


More information about the Cloud-marketplace-proposal mailing list

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