Developing and managing digital service ecosystems: a service science viewpoint

Abstract

Purpose – The need for modern enterprises to seamlessly interoperate poses significant challenges on their capabilities for engaging in multiple business networks. This paper considers a particular type of business network, namely, “service ecosystems”, and proposes architecture for enabling business firms to: control dissemination and usage of the resources they contribute to the ecosystem; and develop corresponding service offerings. Design/methodology/approach – A literature review informed our research work and contextualized the development of relevant research questions. The research questions were based on unstructured, creative techniques (e.g. brainstorming), combined with rigorous requirements specification for software tools developed as part of this research. Overall development was based on service science and enterprise interoperability research, distilled in four principles that provided the context and direction for this work. Findings – Three key components of the proposed architecture were developed: service map, which identifies the building blocks needed to construct a service ecosystem; interoperability model, as a decision-making mechanism for dynamic (re-) arrangement of a service map’s building blocks; and shared service infrastructure for the provision of support services to all ecosystem participants. Originality/value – This research has advanced current thinking in developing and managing service ecosystems. By adopting a service science viewpoint (service value co-creation, value-in-use), a holistic approach for building collaboration capabilities is described: at the enterprise level, it pertains to decision-making mechanisms for service provision; at the ecosystem level, it pertains to a software platform for managing common collaboration tasks.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 33 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.