[Fiware-boost-rural] WP structure - Task level details

[Juanjo Hierro]

Dear all,

   First of all, I hope you have received this mail well because it is 
being sent through the mailing list we have created for elaboration of 
the proposal.  For sending mails to the mailing list, you should use the 
address:

    fiware-boost-rural at lists.fiware.org

   Second, we want to share a document with description of WPs and tasks 
<https://docs.google.com/document/d/1q1VOIREsurIQo8PRaVCTgmmBTEeOD-5p7ustT6AFBCY/edit?usp=sharing> 
as input for the discussion tomorrow.

   Some comments (and open questions we invite you to think about):

  * Regarding WP2:
      o We have to bear in mind that the cross-sector digital platform
        to be deployed in a given region for pilots in that region will
        comprise:
          + A number of base general-purpose platform components coming
            from FIWARE which can be combined with best-of-breed
            third-party open source components (e.g., Spark)
          + A number of components to be developed in the pilots which
            have the potential to be reused in multiple regions (with
            the potential to be contributed to FIWARE as a mean for
            sustainability beyond duration of the project)
      o Evolution/maintenance and support of the first group will take
        place in WP2
      o Our proposal is that development and support of the second group
        will take place in WP4 (Pilots implementation) even though will
        be coordinated from WP.  Rationale is that it will be very
        difficult to identify "a priori" how much of the development to
        be carried out by regional partners will be addressed with the
        intend of generate reusable components and therefore it will be
        difficult to estimate a priori how such partners could
        distribute their resources between WP4 and WP2 (where we would
        need to add them as partners if reusable components identified
        in the pilots had to be implemented in WP2).
  * Regarding WP3:
      o We proposed some tasks which were considered in projects where
        there was also an initial phase which had to do with
        participatory ideation and design of services.  However, we are
        happy to adapt to whoever wishes to lead the WP.
      o Ditte: your comments are more than welcome here and if your
        organization wants to lead the WP it would be great as well.
  * Regarding WP4:
      o Aspects to consider are tri-dimensional:
          + Focus areas:  Public Services, Primary Sector, New Economy,
            Energy, Tourism
          + Dimensions to consider: Economical, Socio-cultural, Legal,
            Educational, Technological
          + Actions: Spaces re-visited, Resources re-discovered,
            Community re-inforced, Services re-invented, Agency
            re-vitalizeed
      o However, we need to come with a list of tasks.
      o Beneficiaries from the Open Calls have to be incorporated, with
        the resources that they will get funded, in tasks of this WP so
        the approach of defining one tasks per region from the original
        consortium doesn't work.
      o Therefore, we see two approaches for definition of tasks:
          + We may consider that tasks may be linked to phases of the
            pilots (implementation of services, deployment,
            operation/validation) but then we have to figure out how we
            will manage the fact that some of the services will be
            provided by beneficiaries from the Open Calls.  An option
            could be that once scope and concrete services for pilots
            have been identified in WP3, we will identify which services
            will be implemented by members of the original consortium
            (solution integrators/developers proposed as members of the
            original consortia) and which ones will be selected through
            open calls.
          + We simply map tasks to focus areas and describe the kind
            services, etc. that will be developed in each
      o For the time being, we have gone for the option of defining
        tasks per focus areas because the first option could be a bit
        tricky to explain, but let's discuss that tomorrow.
      o In any case, a task for overall coordination of the pilots is needed
  * Regarding WP5:
      o We have arrived with an initial proposal based on approach taken
        in similar projects
      o However we welcome feedback from partners interested in leading
        this WP: Peyman, we welcome your offering here and look forward
        your specific comments
  * Regarding WP6:
      o This WP will be coordinated by the FIWARE Foundation with strong
        support from FundingBox (Community Management).  Of course
        active participation of partners.
  * Regarding WP7:
      o We have arrived with an initial proposal based on approach taken
        in similar projects.
      o We need someone who may lead this WP or propose partners which
        own credentials to carry out the tasks
  * Regarding WP8:
      o FundingBox should review the structure (which comes from another
        project where they were managing thee cascade funding and had
        precisely a WP for dealing with cascade funding)

   I hope this provides good food for thought in preparation of the 
meeting tomorrow.

   Cheers,

-- 
Document
Juanjo Hierro
Chief Technology Officer
juanjose.hierro at fiware.org <mailto: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/fiware-boost-rural/attachments/20200304/ff7482be/attachment.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/fiware-boost-rural/attachments/20200304/ff7482be/attachment.png>