Open Innovation 2.0 Yearbook 2013 - European Commission - Europa
Open Innovation 2.0 Yearbook 2013 - European Commission - Europa
Open Innovation 2.0 Yearbook 2013 - European Commission - Europa
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
96 O P E N I N N O V A T I O N 2 0 1 3<br />
The EUE research programme is using cutting-edge<br />
techniques for spatial data acquisition. These are<br />
applied to, and combined with, concepts for a digital<br />
ubiquitous ecosystem in Espoo City T3 area. The target<br />
application will be a mobile and virtual smart city<br />
model with geospatial virtual knowledge elements.<br />
Specific attention will be paid to aspects of usability<br />
and innovative visualisation for various user needs.<br />
By capturing the city’s geometry and characteristics<br />
through laser scanning, the resulting model can<br />
be applied in an information modelling process to<br />
conduct different kinds of analysis. The virtual —<br />
possibly, photorealistic — models used as the basis<br />
for the regional information model create a virtual<br />
city, geometrically accurate and visually close-toidentical<br />
with the real one. This enables city planning,<br />
built environment and real estate management<br />
professionals, as well as decision-makers<br />
and citizens, to use the model for diverse purposes.<br />
An integral part of the ongoing RDI process is<br />
the Meshmoon online virtual reality hosting system,<br />
which is based on on-demand cloud-hosting<br />
technology and the open source realXtend Tundra<br />
software.<br />
The EUE programme’s initial results have also made<br />
diverse issues and challenges explicit. It is clear<br />
that one of the key challenges now is orchestration.<br />
<strong>Innovation</strong> in networks cannot always be managed:<br />
often orchestration — the process of creating conditions<br />
and support infrastructure whereby innovation<br />
can emerge and be sustained — is required.<br />
Many innovation management processes in organisations<br />
are reasonably well understood and documented,<br />
while the processes of orchestrating open<br />
innovation networks and innovation ecosystems<br />
are neither well documented nor understood adequately.<br />
The processes involved in creating, supporting<br />
and maintaining a regional innovation<br />
ecosystem in which diverse actor groups participate<br />
— large industries and SMEs, local municipality<br />
bodies, knowledge institutions with diverse<br />
researchers working in a range of different fields<br />
of expertise, and many other actors — are often<br />
complicated, sometimes complex, and need to be<br />
developed in situ as the ecosystem itself emerges.<br />
Orchestration is not the same as<br />
management<br />
As in many large innovation programmes, participating<br />
actors have the ambition to collaboratively<br />
create innovative products and services which can<br />
be applied locally and compete in global markets.<br />
In practice, however, participants tend to focus on<br />
their own tasks, sectors, organisations and disciplines,<br />
working to optimise their own work, often with<br />
inadequate attention for the work of network partners<br />
(in other work packages, and elsewhere in the<br />
ecosystem), who, on the surface, seem to be dealing<br />
with different issues altogether. The deeper the focus,<br />
the more difficult it is for results-oriented researchers<br />
and business interests to develop the trust, respect,<br />
and mutual understanding needed to overcome the<br />
effects of their working silos: inadequate communication,<br />
insufficient connection, ineffective search facilities.<br />
Typical problems encountered are that the entire<br />
ecosystem suffers from their inability to find answers<br />
to questions that their network partners have already<br />
answered, and that the wheel is too often reinvented.<br />
All can benefit from support infrastructure and facilitation<br />
that enhances the required sharing of knowledge,<br />
resources and results. This is the primary task<br />
of good orchestration.<br />
Orchestration is not the same as management.<br />
In an innovation ecosystem, it is not possible to<br />
manage many aspects of the innovation process.<br />
Orchestration is needed; this relates to both:<br />
1. the capacity to create conditions where the<br />
diverse parties can work together with the right<br />
balance of inner and outer focus and, thus, reinforcing<br />
both their own work and benefiting the<br />
ecosystem as a whole; and<br />
2. the provision of supporting service infrastructure<br />
to help sustain effective operation within<br />
the system.<br />
One needs to know how to organise the right methods,<br />
tools and facilitation processes to help projects<br />
and partners achieve their objectives. The methods<br />
may range from tools and technologies for creative<br />
problem-solving, user-centred co-creation, building<br />
synergies and breaking silos, to finding ways to deal<br />
with resistance to change and create breakthroughs<br />
in stuck situations. In addition, a systemic learning<br />
infrastructure is needed to ensure effective learning,<br />
and to facilitate entrepreneurial learning — the rapid<br />
application of lessons learned within the ecosystem<br />
so that projects and players can systematically<br />
benefit from each other’s experience and expertise.<br />
Processes for benchmarking (accessing and applying<br />
relevant and inspiring lessons and good practice<br />
from diverse sources around the world) and benchlearning<br />
(a collaborative, symmetric learning process<br />
based on peer-to-peer exchange) are also essential.<br />
Modernising the triple helix means engaging in<br />
a transformation process for the systemic development<br />
of regional innovation ecosystem. Orchestration<br />
activities should be developed up to the level of<br />
smart orchestration, which implies: