Task Force Innovation
-
Upload
iot-epi -
Category
Technology
-
view
96 -
download
0
Transcript of Task Force Innovation
Workshop TF InnovationSUMMARY
June 23rd 2016, Valencia
Laura Kohler (Be-IoT), Michele Nati (Unify-IoT), Vincent Demortier (Be-IoT)
Agenda WORKSHOP AGENDA
09:00 Session introduction (15 mins) – Moderated by Laura K.• Overview of task force mission and objectives• Summary of current progress and initial key findings regarding innovation eco-systems and open calls
09:25 Innovation ecosystem workshop (Overall 90 mins)a. Interactive (60 min)i. Eco-system mapping exerciseii. Brainstorming of ideas and strategies for fostering adoption and ecosystem growthb. Group presentations (30 min)
10:45 Coffee Break
11:15 Remote Keynote by Ingrid Willems & Ingrid Moermann (iMinds): Open Call Best Practices (45 mins)
12:00 Open Call Alignment (Common Message & Activities) (overall 70 mins)a. Interactive (40 min)i. Discussion of success factors of open callsii. Alignment of common messageiii. Creation of first ideas for common open call activitiesb. Group presentations (30 min)
13:10 Lunch break
Agenda
Be-IoT: Laura Kohler, [email protected]
Be-IoT: Richa Sharma, [email protected], FhG
Be-IoT: Vincent Demortier, [email protected], Faubourg
Numérique
Unify-IoT: Alex Gluhak, [email protected], DIGICAT
UNIFY-IoT: Maurizio Spirito, [email protected], ISMB
UNIFY-IoT: Philippe Moretto, [email protected], ETSI
BIG-IoT: Ivano Gauna, [email protected], CSI Piemonte
BIG-IoT: Lisa Cosmi, [email protected], CSI Piemonte
BIG-IoT: Claudia Simonato, [email protected], CSI Piemonte
INTER-IoT: Regel González, [email protected], UPVLC
INTER-IoT: Pasquale Pace, [email protected], UniCal
INTER-IoT: Luisa Escamilla, [email protected], VPF
Participants
VICINITY: Stefan Vanya, [email protected], BVR
symbIoTe: Oliver Barreto Rodriguez, [email protected], ATOS
symbIoTe: Maria Bianco, [email protected], CNIT
AGILE: Charalampos Doukas, [email protected], CREATE-NET
AGILE: Fabio Antonelli, [email protected], CREATE-NET
AGILE: Nils Walravens, [email protected], iMinds
TagItSmart!: Liisa Hakola, [email protected], VTT
TagItSmart!: Kaisa Vehmas, [email protected], VTT
bIoTope: Petra Turkama, [email protected], Aalto Univ. School of BusinessbIoTope: Arkady Zaslavsky, [email protected], CSIRO Australia
Everyone who participated in the workshop mark or add your name in red below. If colleagues from your consortia participated who are not on the mailing list, please add them here and share the minutes.
AgendaINTRODUCTION (Slides 5-16)
• The workshop was hosted by Laura Kohler (Be-IoT, etventure) and supported by Michele Nati (Unify-IoT, Digital Catapult) and Vincent Demortier (Be-IoT, Faubourg Numerique). Alex Gluhak (Unify-IoT, Digital Catapult) had to cancel last minute due to unforeseen travel difficulties.
• The introduction was used to go through mission statement & objectives of TF01 (see slides 4 & 5) and to give an overview on the first results of the task force on (a) innovation eco-system building (slides 6-11) and (b) open call alignment (slides 12-16).
• The first findings on innovation ecosystem building cover four different topics: (a) collection of main drivers (technical & non-technical), (b) collection of main barriers (technical & non-technical), (c) clustered support needs, (d) clustered target users. Those findings revealed as main support needs “community building and stakeholder engagement” and “communications and dissemniation”, the main target users approached by all projects are “IoT platform operators”, “IoT service developers”, “IoT service providers” and “end users”
• The first findings on open call alignment show that common promotion activities are possible due to overlaps in open call timings (e.g. Inter-IoT and SymbIoTe will start in Q4/2016). First fact finding revealed that the most projects plan one or two open calls, that funding per call is between 150k and 850k and that important details such as number of projects and funding per project are not yet defined. The main support needs are “open call promotion / common message” as well as “Sharing best practices”. Goals and USPs for the open calls have to be defined as well as common activities.
Agenda
MISSION
Foster a successful innovation ecosystem for the Internet of Things in Europe.
OBJECTIVES
• Design Efficient Innovation Management Process for EPI• Common activities to address drivers and barriers of innovation ecosystems;
e.g. joint initiatives to move towards a single digital market for IoT• Open Calls with real impact• Best practices / guidelines to accelerate product and service innovations on top
of EPI platforms by third parties (how to make platforms more accessible for developers, how to engage with developer ecosystems)
MISSION & OBJECTIVES
Innovation Ecosystems
Road to Valencia:
April: Task force kick off - agreement on common mission statement and objectives.
May: Identification of main drivers and barriers of IoT innovation ecosystems, discussion of main support needs of the IoT-EPI projects
June: Identification of unique value propositions of RIA projects and target stakeholders for engagement
Today: a) Understanding of innovation barriers and drivers faced by the IoT-EPI projectsb) Understanding of support needs of the IoT-EPI projects - main concerns are clear communication and
stakeholder engagementc) Understanding of unique value propositions of most project IoT-EPI projectsd) First understanding of important stakeholder categories IoT-EPI need to engage with
Technicala) Tools for simplifying IoT deploymentb) Tools for guiding interop processesc) Multi-tech expertise across verticalsd) Real world trial sitese) Trust mechanisms between IoT
platformsf) Dedicated APIs
Non-technicala) Clear communication of value
propositionsb) Effective stakeholder engagementc) Effective collaboration across value
chaind) Opennesse) Right regulatory frameworkf) Incentivesg) New business modelsh) Reduced time to market
Drivers
Technicala) IoT standards jungleb) Closeness of IoT platformsc) Lack of trust mechanismsd) Lack of semantic alignmente) Reliability of integrated systems
Non-technicala) Lack of community tractions and
stimulation of demand/supply b) Lack of willingness to federate and
open upc) Inadequate legislationd) Lack of stakeholder collaboration
along the value chaine) Inadequate info/documentation
about IoT platforms
Barriers
AgendaInnovation support needs
AgendaTarget users - EPI projects
AgendaInnovation ecosystems - Next Steps
Today:a) From stakeholder categories to real stakeholders (Identify real communities
for engagement and prioritize them)b) Common ideas and strategies for fostering adoption and ecosystem growthc) Common activities (Create a common action plan) d) IoT-EPI Alignment (Align those outcomes with other task forces)
Road to Valencia:
April: Collection of needs for support for promoting / carrying out open calls.
May: Discussion of main needs & collection of open call timings and further plans.
June: Presentation of open call timings and main plans for open calls.
Today: a) Clear understanding of success factors of open callsb) Formulation of common messagec) Create first ideas of synergies between several RIAS open calls
Open Call Alignment
OPEN CALL TIMINGS
Month Q4/2016 Q1/2017 Q2 / 2017 Q3 / 2017 Q4 / 2017 Q1 /2018 Q2 / 2018 Q3 / 2018 Q4 / 2018
BIG-IoT 1 Open Call: Published April 2017 / closed June 2017
InterIoT 1 Open call: Open October 2016 and close in January 2017
bIoTope Only 1 round of calls. Calls will be published at M17, and closed at M21
symbIoTe 2 Open Calls + 1 Contest (Hackathon) - 1st Open Call: M11 (end of Nov 16) until M15 (beg. of March 17)
2nd Open Call: M22 (end of October 2017) until M26 (beginning of February 2018)
AGILE 2 open calls: M20 and M26. Each will last 8 months
2 open calls: M20 and M26. Each will last 8 months
Vicinity No final planning agreed yet on detailed planning. 2-3 in 2017 late as of now.
TagItSmart 2 calls, second and third year
AgendaOPEN CALL OVERVIEW
Project No. of Calls Funding per call Number of projects Funding per project
BIG-IoT 1 750.000 €
InterIoT 1 850.000 €
bIoTope 1 750.000 € 60-150k
symbIoTe 2 220.000 € / 460.000 € 1st Call Level 1: 2 -3 Proposals
Level 2: 2 proposals2nd call
Apps: 2 - 3 proposalsTrials: 2 proposals
1st callLevel 1: approx 30K euro per each
Level 2 : 60k euro per each2nd call
Apps: approx 40k euroTrials: 80K euro
AGILE 2 400.000 € 16 60k
Vicinity 2'-3 150.000 € - 250.000 €
TagItSmart 2 600.000 € >8 >150k
AgendaOPEN CALL OVERVIEWBIG-IoT InterIoT bIoTope symbIoTe AGILE Vicinity TagItSmart
USPOpen IoT ecosystemlowering market entry barriers for IoT ecosystem stakeholders We do not develop yet another platform. Instead, we reuse and build up on existing methods to allow interweaving of existing and future IoT platforms, smart objects, and users.
We provide an interoperability framework and associated methodology that may allow the interoperability of multiple platforms.
Relevant use cases with real market potential, experienced and representative project team, ambitious project with expectations for disruptive, new to market, new to the world solutions.
We shape an interoperability framework allowing various platforms to collaborateApplication developers can create innovative applications based on the collaboration of multiple IoT platforms (addressing cross-domain needs).
technological Joining a vivid, bottom-up approach to create interoperability in the IoT; create new services for the IoT based on cloud-based interoperability solution.
We have cool platform with a lot of potential use cases
Technology, combined with end users willing to test services.
Ser- vices
Dedicated contact person, Collaboration platform, Workshops
dedicated contact person, support of the partners in order to succeed in integration
allow access to a new network and competence pool, new business opportunities and learning
support and troubleshooting by project partners;documentation for the software to be used; support in certain technical aspects; access to team collaboration platform and mailing lists for direct communication
Support for integrating/extending and adapting AGILE software and hardware in their product/services; mentoring and business exploitation support by Startupbootcamp
Access to cloud-based solution for development of interoperable devices, services, architectures;model-based framework for model-based development process
To be defined
What makes you special? (Interoperability is not a USP)
AgendaOPEN CALL Next Steps
Today:a) Common knowhow (Learn from two experts outside of IoT-EPI, understand
success factors)b) Common message (Start formulating a common message & define
responsibilities)c) Common activities (Create a common action plan) d) IoT-EPI Alignment (Align those outcomes with other task forces)
AgendaINTERACTIVE SESSIONS PART 1Innovation ecosystem building
• The interactive sessions on innovation ecosystem building focused on a mapping of the main stakeholders and common activities for platform adoption. To do so, the group split into two parts and worked on both topics with the two facilitators Michele Nati and Laura Kohler for about one hour. Afterwards the two groups presented their outcomes.
• Summary of outcomes of group 1a (stakeholder mapping): Objective of the session was to complete the stakeholder mapping activity by identifying real stakeholders names for each category. The group initially focused on defining and gaining a common agreement on what each category means. Some confusion might exist. Not all the projects requires all the categories. Recommendation is that stakeholders should cover those functions/organizations required to realize the vision and ambition of the project. Ideally each project should include a representative of each required stakeholder. The ecosystem should represent all the functions/organizations required to exploit the project outcome and create new value out of this. The provided categories cover both. It might be better to talk in general about ecosystem and each project should then identify which subset of categories represent its stakeholders set and which one is ecosystem/exploitation set. After an agreement on categories was reached, projects representatives tried to give names for businesses they might see as partners in each category. It emerged that when considering exploitaiton partners, all the projects are developing B2B solutions, not targeting directly end-users, e.g., through a mobile app. Most of the projects don’t currently have clear idea about businesses they need to partners with. In terms of ecosystem development recommendation is that they need to identify a use case, then identify an IoT service providers, e.g., problem owners that might benefit from the project and leverage on this service providers network, e.g., it become a champion for the project, to identify businesses developing new services using the project.
• Summary of outcomes of group 1B (common activities for adoption): The group decided to focus on three target groups: (a) developers, (b) system integrators, (c) end users. The group agreed that adoption amongst developers will be the starting point - however adoption by end users will be even more important as those will have an influence on the platform decisions made by system integrators (and for many projects those are the main customers, e.g. Inter-IoT). The group started brainstorming ideas for fostering adoption amongst developers - such as activities at Universities, fancy show cases for students, a developer-focused website, events that connect end-users with developers to work on existing problems, idea challenges, hackathons, artefacts in open source communities, be very clear on open API / open source, attract hacker spaces. Adoption amongst end-users could be fostered by reaching out to DIY communities (maker kits), finding evangelists amongst end-users (living labs), identify different groups (disruptors versus efficiency seekers) and have targeted activities.
AgendaWorkshop - Session 1a: Innovation ecosystem - stakeholder mapping
AgendaWorkshop - Session 1b: Innovation ecosystem - Ideas and strategies for adoption
AgendaINTERACTIVE SESSIONS PART 2Open call alignment (1/2)
• The session about open call alignment started with two presentations by Ingrid Moerman (Wishful Project) and Ingrid Willems (Create-FI Project) - both iMinds. The two of them presented their project as best practices for open calls and talked about their learnings and the main success factors. Both presentations were uploaded to the Google Drive folder TF Innovation / Workshops.
• The interactive sessions focused on the three topics “Main success factors of open calls”, “Common Open call message” and “Common community building activities” - led by Vincent Demortier (Be-IoT, Faubourg Numérique).
• Summary of outcomes of group 2a (collection of success factors): Participants from projects first reminded that the main expected outcomes of the calls are (by order of priority):
• developer community building and technical feedback • new use cases or extension of pilot use cases• technology integration in business applications
Then the group identified some important factors to achieve the above expected results: • Clear and simple application process from developers and startup points of view• Transparency about the level of maturity (TRL level) expressed in common language and in terms of objective: improve the
technology / integrate the technology • Do not neglect the “losers”: all the applicants to the calls have showed an interest for the projects and the technology, they all
might be the basis to initiate a developer community, no matter if they are selected for sub-grants through the calls or not.Finally it appears that there is no experience in the group for Open Call organisation: support from other projects RIA+CSA is welcome.
AgendaINTERACTIVE SESSIONS PART 2Open call alignment (2/2)
• Summary of outcomes of group 2b (common message): Before compiling a common message for the open calls, the projects represented in the session presented the main USPs of their open call strategies: SymbIoTe = creating added value by connecting several domains, Inter-IoT = inter-domain use cases, Vicinity = technology adoption / co-creation (wider approach), bIoTope = developing further own solutions → starting from this basis the group agreed on the main underlying message for the open calls: “IoT-EPI is the community that will define the future of IoT in the EU / worldwide”. On top of that the following concrete value propositions for all open calls were defined: fast deployment, innovation booster, grants, test solutions with leading players in the industry, disruptive solutions, visibility.
• Summary of outcomes of group 2c (common community building activities): Aim of the sessions was to identify a set of common activities to help with promotion of open calls and realization of a successful open call, with adequate number of good quality proposal. A first suggestion was to create a ‘yellow page’ of all the open calls under the IoT-EPI and EU websites with link to specific project and open call dedicate page. All the projects will help to point perspective applicants to this unique entry point. It was additionally agreed that target communities should be reached with promotion of the open calls. Some communities might be easily part of one project ecosystem, due to some of the project partners relation, but not being included in the ecosystem of the project actually benefitting from them for its specific open call. Recommendation is that each project should circulate a list of gaps they identify in their ecosystem, and eventually other projects having contacts with the identified missing community might decide to help their sister RIA project with promotion of their open call in such community..
AgendaWorkshop - Session 2a: Open Call Alignment - Success factors (1/2)
AgendaWorkshop - Session 2a: Open Call Alignment - Success factors (2/2)
AgendaWorkshop - Session 2b: Open Call Alignment - Common message
AgendaWorkshop - Session 2c: Open Call Alignment - Common community building activities