<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The D-BEST based Service Portfolio Configuration for Incubator Ecosystems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Cristobal Costa-Soria</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Claudio Sassanelli</string-name>
          <email>claudio.sassanelli@polimi.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Management, Economics and Industrial Engineering</institution>
          ,
          <addr-line>Politecnico di Milano, Piazza Leonardo da Vinci, 32, 20133 Milan</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Department of Mechanics</institution>
          ,
          <addr-line>Mathematics and Management, Politecnico di Bari, Via Orabona 4, 70125, Bari</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>ITI - Instituto Tecnológico de Informática</institution>
          ,
          <addr-line>Camino de Vera s/n, 46022 Valencia</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The configuration and organization of a service portfolio when different organizations or service providers are involved is far from being trivial. This is specifically the case in incubator ecosystems, where different competences and providers are involved to effectively prepare startups to go to a very competitive market. This paper describes the experience of the REACH Data Incubator for organizing its service portfolio, and how the D-BEST service model was applied to implement its catalogue. This work presents the needs that motivated the use of a service model, how the services were organized, and which advantages and drawbacks were found during the development and application of the service model.</p>
      </abstract>
      <kwd-group>
        <kwd>1 Service catalogue</kwd>
        <kwd>service model</kwd>
        <kwd>service portfolio configuration</kwd>
        <kwd>incubation services</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        In the context of networked organizations [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], such as Digital Innovation Hubs [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] or Incubation
ecosystems, a key activity is the design and configuration of the service portfolio. This service
portfolio aggregates, and enhances in some cases, a wide, diverse, and complementary range of services
from different providers, which are selected and organized according to the mission and value
proposition of the networked organization. For instance, in the case of an incubation ecosystem, such as the
REACH Incubator [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], the service portfolio involves technology training and support services,
business development services, and access to finance services, with the goal of preparing their customers
(entrepreneurs and startups) to face a very competitive market.
      </p>
      <p>The configuration of networked organization service portfolios could be very complex, because
depending on the number of service providers involved, and the service offer that each provider might
bring to the portfolio, the number of services included could be large and difficult to manage. There
might be different types of services, with different requirements and outcomes, and different ways of
being classified. Then, an important decision to take is how to organize such a large service portfolio
in a way that is easily browsable and accessible by their target customers, but also that facilitates
agreement with all the involved service providers.</p>
      <p>
        This paper describes the REACH experience for configuring and deploying its service portfolio,
and how the Data-based Business-Ecosystem-Skills-Technology (D-BEST) model [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] was applied in
the context of an incubator ecosystem. This work presents the needs that motivated the use of a
service model, how the services were organized and why, and which advantages and drawbacks were
found during the development and application of the service model.
      </p>
      <p>This paper is structured as follows. Next section introduces the REACH Incubator and the REACH
Service Catalogue, and the need that motivated the use of the D-BEST Service Model. Then, section 3
presents a short overview of the D-BEST service model. Section 4 presents how the D-BEST model
was applied to implement the REACH Service Catalogue. Finally, section 5 presents the conclusions
of the work and further steps.</p>
    </sec>
    <sec id="sec-2">
      <title>2. REACH Incubator and the service catalogue</title>
      <p>
        REACH [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] is a European incubator for data-fuelled start-ups &amp; SMEs, that aims to facilitate the
development of trusted and secure innovative solutions based on industrial and personal data. The
REACH incubation ecosystem is composed of Data Providers, Start Ups &amp; SMEs, Investors and
Digital Innovation Hubs. For Start Ups and SMEs, as incubated companies, REACH provides different
services and assets, such as:
1. A big data infrastructure available to launch data analytics jobs and deploy the Minimum
Viable Products (MVPs) or applications,
2. A network of data providers which propose their business challenges and offer secure and
controlled access to their proprietary datasets to use when targeting these challenges,
3. Access to digital and business skills, in form of data mentoring and business coaching to help
companies to develop their experiments and turn them into market-ready solutions,
4. Ready-to-use tools and state-of-the-art technologies for increasing trust and security in data
sharing and exchange (blockchain, data anonymisation and minimization components, and tools
for the development of trusted-by-design applications),
5. Promotion and showcasing of solutions developed by the subgrantees.
      </p>
      <p>To provide a single and integrated access point to the all the assets described above, one of the first
activities to be done when starting REACH Incubator was to design and deliver the REACH Service
Catalogue. It was conceived as an online portfolio that could showcase all the services to be provided
by the REACH incubation programme, both to prospective applicants and to those that would be
selected to participate in the programme. Among the different requirements to be addressed, the key
ones, from a market perspective, were the following: (1) to facilitate visibility and access to the
complete service offer; (2) to be easily browsable, facilitating navigation and discovery; (3) to facilitate a
clear service description. Therefore, during the design stage of the involved teams, the question was:
How to organize and describe the service offer as to facilitate quick browsing, easy understanding,
and communication?</p>
      <p>A first attempt of organizing the REACH service offer is shown in Figure 1. Services were
organized around three types of services, according to major groups of services in Incubation Ecosystems,
but then the issue was that all the tree main dimensions of services (Technology, Business and
Finance) were integrated and fuzzy with training and skills activities. Furthermore, the data services
were strictly connected with the technology one, while the ecosystem services seemed to be integrated
into the Finance dimension.</p>
      <p>To this end, service taxonomies are a powerful tool to organize, label, and manage services, since,
as a taxonomy, provide features such as consistency, clarity, simplicity, alignment, and reuse.
However, the issue turned out to decide which service taxonomy to use, as no standardised taxonomy for the
incubation ecosystem domain was identified at this point. After looking up to different service
portfolios and taxonomies closer to the domain of Incubation Ecosystems, the D-BEST service model was
identified as a good candidate to be adopted, for the reasons explained in section 3.</p>
    </sec>
    <sec id="sec-3">
      <title>3. D-BEST reference model: a service taxonomy for DIHs</title>
      <p>
        The D-BEST reference model is a service taxonomy that derives from the I4MS
EcosystemTechnology-Business (ETB) service model [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The D-BEST [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] is an exhaustive and complete
service reference model that is being used by different DIHs and DIH networks across Europe to
organise their service offer in a consistent way. Some examples are DIHNET (https://dihnet.eu), DIH4CPS
(http://dih4cps.eu), or DIH4INDUSTRY (https://dih4industry.eu/), among others. The D-BEST service
model defines 5 macro-classes on which the services are organised: (1) Ecosystem, covering
communication and community building activities; (2) Technology covering hardware/software
development/support activities; (3) Business, for business development, planning and access to financial
pools; (4) Skills for maturity assessment, human up-skilling and training; and (5) Data, bringing
capabilities and support for data acquisition and sensing, processing &amp; analysis, decision-making, data
sharing.
      </p>
    </sec>
    <sec id="sec-4">
      <title>4. Application of D-BEST to describe REACH services</title>
      <p>Although the D-BEST Service Model is defined for DIH service portfolios, or DIH Networks, it
could be easily applied to/adopted in Incubation Ecosystems, since some of the incubation services
are already covered by the categories provided by the model. Therefore, the service taxonomy
proposed by the D-BEST reference model was adopted to implement the REACH Service Catalogue with
the aim of facilitating the exploration and identification of services in a consistent way to other
European service catalogues that are being developed and implemented by DIHs and DIH Networks. As a
result, the REACH Service Catalogue is accessible as a web page (Figure 1), implemented as a
singlepage client-side web application, to facilitate delivering lightweight and responsive contents for
different devices (desktop, mobile, tablets). The REACH service offer is implemented in a database,
which is used by the backend to dynamically generate the list of services that are shown to the user.
This design decision facilitates the updating of the service offer and the descriptions without the need
to changing the user interface, thus facilitating service portfolio updating.</p>
      <p>Even if the REACH service catalogue has been grounded based on the D-BEST reference model,
the user has the possibility to look for specific services using a set of different filters: not only the
DBEST service classification (i.e., the macro-classes (1st level) and types (2nd level) of services of the
reference model), but also the service providers (i.e., the list of providers belonging to the REACH
network), the service outputs (i.e., consultancy, events, funding, network empowerment, sharing of
ideas, sharing of physical assets, support technological business management, technology, training),
and/or the incubation stages (i.e., explore, experiment, evolve, expose).</p>
      <p>In total, 76 incubation services were included in the first version of the REACH Service Portfolio.
The Table 1 presents the number of services that were instantiated per REACH incubation stage (1st
column), per D-BEST macro-class (2nd and 3rd column), and type of service (4th &amp; 5th columns).</p>
      <p>It can be observed that most of the offer is organized around the Experiment stage, where the MVP
development efforts are located, and thus the services are supporting the technical development. This
differs from the last stages, where the focus is the go-to-market, and thus the services are organized
around business development.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Results &amp; conclusions</title>
      <p>
        This paper presented a first attempt of applying the D-BEST reference model, usually applied to
configure the service portfolio of a DIH or a DIH network, to an incubation ecosystem. Within
REACH, the D-BEST service model turned out to be successful also in this domain, triggering a
better management of the value proposition offered by the different service providers of the incubator,
and also facilitating the understanding of which kind of services were more useful in each stage of the
incubation process. Indeed, the incubation stages (i.e., explore, experiment, evolve, expose) can be
used as incubation path templates to be adopted within the D-BEST based DIH Customer Journey
(CJ) analysis method [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] to develop the typical paths of the incubated companies through the support
of the REACH ecosystem.
      </p>
      <p>A drawback that was observed during the application of D-BEST is that some services could be
classified under more than a macro-class or service category. For instance, the service “Access to Big
Data Stack tools” could be classified as “Data and AI &gt; Data processing &amp; analysis”, since it provides
data storage and data analytics infrastructure, but also as “Technology provision &gt; Provision of
infrastructure”. This adds complexity both to the implementation of the service database (many-to-many
relationships) and to the collection of data (the service provider might miss selecting categories). This
was addressed by classifying the service on the closest category to the target domain, i. e. the “Data”
macro-class. Another drawback is that the “Ecosystem building” macro-class was originally designed
to classify DIH- or network- building services. In the incubation context, this macro-class has been
used to classify services oriented towards the development of the network and positioning of the
incubated company (thus supporting its go-to-market): access to brokerage/B2B meetings, access to
relevant events, marketing &amp; communication, etc.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Acknowledgements</title>
      <p>This work has been supported under the European Union’s Horizon 2020 research and innovation
programme under Grant Agreement no. 951981.</p>
    </sec>
    <sec id="sec-7">
      <title>7. References</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>IGI</given-names>
            <surname>Global</surname>
          </string-name>
          ,
          <source>What is a Networked Organization</source>
          ,
          <year>2022</year>
          . URL: https://www.igiglobal.com/dictionary/networked-organization/20224.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>C.</given-names>
            <surname>Sassanelli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Terzi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Panetto</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <article-title>Doumeingts, Digital Innovation Hubs supporting SMEs digital transformation</article-title>
          , in: 27th ICE/IEEE International Technology Management Conference, IEEE, New York,
          <year>2021</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          , doi: 10.1109/ICE/ITMC52061.
          <year>2021</year>
          .
          <volume>9570273</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <article-title>[3] REACH, EuRopEAn incubator for trusted and secure data value</article-title>
          <source>Chains</source>
          ,
          <year>2022</year>
          . URL: https://www.reach-incubator.eu.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>C.</given-names>
            <surname>Sassanelli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Panetto</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Guedria</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Terzi</surname>
          </string-name>
          , G. Doumeingts,
          <article-title>Towards a reference model for configuring services portfolio of Digital innovation hubs: the ETBSD model</article-title>
          ,
          <source>IFIP AICT 598</source>
          (
          <year>2020</year>
          )
          <fpage>597</fpage>
          -
          <lpage>607</lpage>
          , doi: 10.1007/978-3-
          <fpage>030</fpage>
          -62412-5_
          <fpage>49</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Butter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Gijsbers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Goetheer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Karanikolova</surname>
          </string-name>
          ,
          <article-title>Digital innovation hubs and their position in the European, national and regional innovation ecosystems</article-title>
          , in: Redesigning Organizations:
          <article-title>Concepts for the Connected Society</article-title>
          , Springer, Berlin,
          <year>2019</year>
          , pp.
          <fpage>45</fpage>
          -
          <lpage>60</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>030</fpage>
          - 27957-
          <issue>8</issue>
          _
          <fpage>3</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>C.</given-names>
            <surname>Sassanelli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Gusmeroli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Terzi</surname>
          </string-name>
          ,
          <article-title>The D-BEST based Digital Innovation Hub customer journeys analysis method: a pilot case</article-title>
          ,
          <source>in: 22nd IFIP WG 5.5 Working Conference on Virtual Enterprises, PRO-VE</source>
          <year>2021</year>
          ,
          <article-title>Saint-</article-title>
          <string-name>
            <surname>Etienne</surname>
          </string-name>
          ,
          <year>2021</year>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>030</fpage>
          -85969-5_
          <fpage>43</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>