Refine
Year of publication
- 2021 (15) (remove)
Document Type
- Article (1)
- Book (2)
- Part of a Book (2)
- Conference Proceeding (6)
- Internet Paper (1)
- Report (1)
- Working Paper (2)
Is part of the Bibliography
- no (15)
Keywords
- ADAM (1)
- Autonome Elektromobilität (1)
- Business Applications (1)
- Cyber Security (2)
- Cyber-Security (1)
- Cybersicherheit (1)
- Digital Architecture Management (1)
- Digital Transformation (2)
- Digitalisierung (2)
- Digitalization (2)
Institute
- Informationsmanagement (15) (remove)
Smart Service Prototyping
(2021)
This chapter is dedicated to prototyping, one of the steps of the Smart Service Engineering Cycle. It includes three phases: realizing core functionalities, developing core functionalities, and testing functionalities with customers. In order to realize prototypes successfully, methodical aspects of rapid IoT prototyping are used.
First of all, this chapter explains the motivation behind rapid prototyping and provides an introduction to the approach. The concept of rapid IoT prototyping is based on the idea of developing short-cycle solution variants on the basis of benefit hypotheses or benefit promises and user stories focusing on them. The aim is to achieve data acquisition, aggregation, linkage, processing, and finally visualization by developing it in a vertically integrated manner. Once this is accomplished, the prototype can be evaluated with customers, which also makes it possible to put the benefit hypotheses to the test. Finally, the collected customer feedback can be incorporated more quickly into the development process of new prototype versions, leading to a continuous improvement of the user experience as well as a constant focus on prioritizing the user. Another component of rapid IoT prototyping is working and thinking in terms of minimum viable products (MVP), i.e., solutions that do not meet all of the defined requirements in the first iteration, but are nevertheless already functional. [https://link.springer.com/chapter/10.1007/978-3-030-58182-4_6]
The digital transformation brings up various new tasks to manage new business application software and integrate them into existing business processes and legacy systems, which are necessary to keep e.g. a production system running. Today, all these tasks are on the one hand not clearly defined and on the other hand, responsibility of these cross-disciplinary tasks is unclear in companies being mostly structured in a function-oriented way. While quality management has developed to a firmly established function of process excellence years ago, IT-application management is still to become an inevitable part of the digital transformation. There are just a few authors trying to define and describe this part, the related tasks, and necessary roles in an organization. In this paper, we show how the business needs of a company can influence the ideal adaptation of the digitization solutions and thus become the success of the digital transformation. We base the paper on a use case in manufacturing companies. We then describe how companies deal with business application systems today. Based on the framework Aachen Digital Architecture Management we describe how a company can holistically improve the management of business application systems.
Low-Level-Code Based Production Model For Improving Material Requirements Planning In ERP Systems
(2021)
Single and small-series production companies face specific challenges, such as variable customer order decoupling points (CODP), decreasing quantities and rising cost pressure. This leads to a increasing production complexity and growing requirements on Production Planning and Control (PPC). Digitalization’s direct links between objects, people, and machines as well as detailed recording of production progresses opens new solutions for PPC. However, volume of data and the required processing times are increasing. Thus, to achieve near-real-time data processing, a decentralization of decision-making systems can be observed. The function Material Requirements Planning (MRP) is PPC’s original need for Enterprise Resource Planning (ERP) systems. Here, PPC’s overall problem (to fulfil primary requirements for products) is divided into subproblems (to fulfil single production orders). Especially companies characterized by an organization in accordance to the workshop principle, high in-house production depth and variable CODP are confronted with high dynamics in their production systems. This ends in significant differences between primary requirements (overall problem) and single production orders (subproblems). Ultimately, these insufficient PPC data result systematically in a non-optimal overall solution despite optimal partial solutions. This publication combines PPC’s fundamentals from existing commonly known models with current implementation concepts of ERP systems. A newly developed Low-Level-Code based Production Model provides explanations for deviations between the overall problem and its subproblems. Furthermore, information flows of PPC can be structured between a periodically actualized vertical and an event driven horizontal information flow. These recognitions lead to an improvement of PPC by ERP systems.
Digitalization and Industry 4.0 continue to shape our industrial environment and collaboration. For many enterprises, a key challenge in moving forward in this matter is the integration of their shop-floor systems (hard- and software) with their office-floor systems to harvest the full potential of industry 4.0.
A multitude of different technologies and respective use-cases available on the market leave many companies startled. This paper presents a set of use-cases for IT-OT-Integration to bring transparency into a company’s digital transformation.
Additionally, a technical requirements profile for integrating IT- and OT-Systems based on the use cases is presented. Both, use-cases and their requirements, guide companies in selecting the digitalization measures that fit their current situation and help in identifying technical challenges that need to be addressed in the transformation process.
Networked digitalisation as an enabler for smart products and data-based business models presents companies with numerous and diverse challenges on their way through the digital transformation. Various reference architecture models have been developed in recent years to support these companies. A detailed analysis of these and in particular their use by companies quickly showed that currently existing reference models have major weaknesses in their practical suitability. With the Aachen Digital Architecture Management (ADAM), a framework was developed that specifically addresses the weaknesses of existing reference architectures and specifically takes up their strengths. As a holistic model, specially developed for use by companies, ADAM structures the digital transformation of companies in the areas of digital infrastructure and business development starting from customer requirements. Systematically, companies are enabled to drive the design of the digital architecture, taking into account design fields. The description of the design fields offers a detailed insight into the essential tasks on the way to a digitally networked company. The model is not only a structuring aid, but also contains a construction kit with the design fields to configure the procedure in the digital transformation. The procedure differentiates between the development of the digitalisation strategy and the implementation of the digital architecture. Three different case studies also show how ADAM is used in industry, what structuring support it can provide and how the digital transformation can be configured. The breadth and depth of ADAM enable companies to take the path of digital transformation systematically and in a structured manner, without ignoring the value-creating components of digitalisation. This qualifies ADAM as a sustainability-oriented framework, as it places the economic scaling, needs-based adaptation and future-oriented robustness of solution modules in the focus of digital transformation.