Refine
Year of publication
- 2021 (21) (remove)
Document Type
- Article (6)
- Conference Proceeding (6)
- Part of a Book (4)
- Postprint (3)
- Contribution to a Periodical (1)
- Doctoral Thesis (1)
Is part of the Bibliography
- yes (21) (remove)
Keywords
- digital platforms (4)
- COVID-19 (3)
- digital learning (3)
- production control (3)
- production planning (3)
- systematic literature review (3)
- ERP (2)
- IIoT (2)
- Industrie 4.0 (2)
- Maschinen- und Anlagenbau (2)
Digital software platforms such as iOS or Android evolve quickly. Through regular updates, their set of built-in (core) features increases. While innovation allows strengthening platforms amidst competition, it can hurt contributors when introducing core features that are already provided by third-party developers (Platform Coring).
This book addresses the underexplored phenomenon of Platform Coring and provides strategical guidance for platform owners and third-party contributors. Platform owners are well-advised to carefully consider the benefits and risks for their platform ecosystem.
The book contributes by highlighting avenues to employ Platform Coring for the competitive advantage of the platform and ecosystem simultaneously.
Future ERP Systems
(2021)
This paper presents a research agenda on the current generation of ERP systems which was developed based on a literature review on current problems of ERP systems. The problems are presented following the ERP life cycle. In the next step, the identified problems are mapped on a reference architecture model of ERP systems that is an extension of the three-tier architecture model that is widely used in practice. The research agenda is structured according to the reference architecture model and addresses the problems identified regarding data, infrastructure, adaptation, processes, and user interface layer.
Today’s mobile devices are part of powerful business ecosystems, which usually involve digital platforms. To better understand the complex phenomenon of coring and related dynamics, this paper presents a case study comparing iMessage as part of Apple’s iOS and WhatsApp. Specifically, it investigates activities regarding platform coring, as the integration of several functionalities provided by third-party applications in the platform core. The paper makes three contributions. First, a systematization of coring activities is developed. Coring modes are differentiated by the amount of coring and application maintenance. Second, the case study revealed that the phenomenon of platform coring is present on digital platforms for mobile devices. Third, the fundamentals of coring are discussed as a first step towards theoretical development. Even though coring constitutes a potential threat for third-party developers regarding their functional differentiation, an idea of what a beneficial partnership incorporating coring activities could look like is developed here.
The idea of the continuous improvement process (CIP) helps companies to continuously improve their operation and thereby contributes to their competitiveness. Through digi tization, new potentials emerge to solve known CIP issues. This contribution specifically addresses the individual motivation of employees to contribute to the CIP. Typically, related initiatives lack contributions over time. The use of gamification is a promising way to achieve continuous participation by addressing the individual needs of participants. While the use of extrinsic motivation elements is common in practice, the idea of this approach is to specifically address intrinsic motivations which serve as a long-term motivator. This article contributes to a gam-ification concept for the continuous improvement process. The main results include an adapted CIP, a gamification concept, and a market mechanism. Furthermore, the concept is implemented and demonstrated as a prototype in an online platform.
Government as a platform?
(2021)
Digital platforms, by their design, allow the coordination of multiple entities to achieve a common goal. Motivated by the success of platforms in the private sector, they increasingly receive attention in the public sector. However, different understandings of the platform concept prevail. To guide the development and further research a coherent understanding is required. To address this gap, we identify the constitutive elements of platforms in the public sector. Moreover, their potential to coordinate partially autonomous entities as typical for federal organized states is highlighted.
This study contributes through a uniform understanding of public service platforms. Despite constitutive elements, the proposed framework for platforms in the public sector may guide future analysis. The analysis framework is applied to platforms of federal states in the European Union.
Die Digitalisierung des deutschen Mittelstandes schreitet weiterhin schleppend voran. So verfügt zwar ein wachsender Teil dieser Unternehmen über vereinzelte Informations- und Kommunikationssysteme, die zielführende Vernetzung und Integration dieser Systeme stellt jedoch weiterhin eine große Aufgabe dar [1]. Besonders vor dem Hintergrund wachsender Bedürfnisse für Informationen und Transparenz sehen sich Unternehmen zunehmend mit der analyseorientierten Nutzbarmachung der Unternehmensdaten konfrontiert [2].
Software platforms allow for the extension of features by third-party contributors. Thereby, platform innovation is an important aspects of platforms attractiveness for users and complementors. While previous research focused the introduction of new features, the aspect of feature removal and discontinued features on software platforms has been disregarded. To explore the phenomenon and motivations for feature removal on software platforms, a review of recent literature is provided. To illustrate the existence of and motivations for feature removal, a case study of the browser platform Mozilla Firefox is presented. The results reveal feature removal to regularly occur on browser platforms for user- and developer-related features. Frequent reasons for feature removal involve unused features, security concerns, and bugs. Related motivations for feature removal are discussed from the platform owner's perspective. Implications for complementors and users are highlighted.
Software platforms regularly introduce new features to remain competitive. While platform innovation is considered to be a critical success factor, adding certain features could hurt the ecosystem. If platform owners provide functionality that was previously provided by a contributor, the owners enter complementary product spaces. Complementary market entry frequently occurs on software platforms and is a major concern for third-party developers.
Divergent findings on the impact of complementary market entry call for the consideration of additional factors. As prior research neglected the third-party perspective, this contribution aims to address this gap. We explore the use of measures to prevent complementary market entry using a survey approach on browser platforms. The research model is tested with 655 responses among developer from Mozilla Firefox and Google Chrome. To explain countermeasures employment, developer’s attitude and perceived likelihood are important. The results reveal that developers employ countermeasures if complementary market entry is assessed negatively and perceived as likely for their extension. Differences among browser platforms concerning complementary market entry are identified. Product spaces of extensions being available on multiple platforms are less likely to be entered and more heavily protected. Implications for research and stakeholders, i.e. platform owners and contributors are discussed.
Modern browsers are digital software platforms, as they allow third parties to extend functionality by providing extensions. In a highly competitive environment, differentiation through provided functionality is a key factor for browser platforms. As the development of browsers progress, new functions are constantly being released. Browsers could thus enter complementary markets by adding functionality previously provided by third-party extensions, which is referred to as ‘platform coring’. Previous studies have missed the perspective of the parties involved. To address this gap, we conducted interviews with third-party and core developers in the security and privacy domain from Firefox and Chrome. This study provides three contributions. First, insights into stakeholder-specific issues concerning coring. Second, measures to prevent coring. Third, strategical guidance for developers and owners. Third-party vendors experienced and core developers confirmed that coring occurs on browser platforms. While developers with extrinsic motivations assess coring negatively, developers with intrinsic motivations perceive coring positively.
Robotic Process Automation (RPA) steht für die softwareunterstützte Bedienung von Softwarelösungen über deren Benutzeroberfläche. Das primäre Ziel, das mit RPA erreicht werden soll, ist die automatisierte Ausführung von Routineaufgaben, die bisher einen menschlichen Eingriff erforderten. Das Potenzial von RPA, Prozesse langfristig zu verbessern, ist allerdings stark begrenzt. Die Automatisierung von Prozessen und die Überbrückung von Medienbrüchen auf der Front-End-Ebene führt zu einer Vielzahl von Abhängigkeiten und Bedingungen, die in diesem Beitrag zusammengefasst werden. Der Weg zu einer nachhaltigen Unternehmensarchitektur (bestehend aus Prozessen und Systemen) erfordert offene, adaptive Systeme mit moderner Architektur, die sich durch ein hohes Maß an Interoperabilität auf verschiedenen Ebenen auszeichnen.