@inbook{11373, abstract = {{The topic of Product Lifecycle Management (PLM) should be nowadays part of any engineering degree course in every university worldwide. In an increasingly digital and connected world, students and prospective engineers need to know the interrelationships of holistic product development. Excellent expertise in a discipline such as mechanical engineering is still necessary, but no longer sufficient. This article explains why this is the case and what universities can do to address this issue. It describes in detail the PLM course of the OWL University of Applied Sciences and Arts located in Lemgo, Germany. In addition, suggestions are made on how to improve the course content, based on many years of experience. As such, this article is a valuable source of information for anyone teaching PLM today or intending to do so in the future.}}, author = {{Deuter, Andreas and Otte, Andreas}}, booktitle = {{Product Lifecycle Management (Volume 6) : Increasing the Value of PLM with Innovative New Technologies}}, editor = {{Stark, John}}, isbn = {{978-3-031-53520-8}}, issn = {{2197-6589}}, pages = {{215--231}}, publisher = {{Springer Nature Switzerland}}, title = {{{PLM in Engineering Education: Purpose and Challenges}}}, doi = {{10.1007/978-3-031-53521-5_14}}, year = {{2024}}, } @inbook{7783, abstract = {{The digitization of the industry, the drive towards smart factories as well as the Internet of Production (IoP) require rising smartness of products and services. Smart physical products are often mechatronic products that include increasing amounts of software. The development of software, however, comes along with new challenges for companies specialized in developing mechanical, electrical or electronic products. Some of these challenges address the product lifecycle management (PLM)-related business and work processes. The management of software lifecycles requires a much more rigorous requirements management. Furthermore, special solutions for management of source code in distributed development teams are needed. The build-process and testing activities need to be conducted in a systematic manner. The generation and provision of different licensing models need to be mastered and finally the issue of security needs to be addressed for any product that can be networked---which by the way is a strategic target of nearly any product developing company. Application Lifecycle Management (ALM) covers many of the above-mentioned issues. IT solutions for ALM are comparable to traditional PLM solutions, but focus particularly on software as a product. Thus, these systems have become widely used by software companies in the same manner as PLM solutions belong to the standard enterprise IT environment of companies developing physical products. With software penetrating traditional physical products, product managers, product developers, manufacturing staff etc. need to work with both, PLM and ALM, since neither solution is able to cover both domains sufficiently. However, ALM and PLM solutions feature redundant functionality. Thus, best practices for the systematic integration of ALM and PLM are required.}}, author = {{Deuter, Andreas and Otte, Andreas and Ebert, Marcel and Possel-Dölken, Frank}}, booktitle = {{Product lifecycle management (Volume 4)}}, editor = {{Stark, John}}, isbn = {{978-3-030-16133-0}}, issn = {{2197-6589}}, keywords = {{Product lifecycle management, Application Lifecycle Management, Smart products, Systems engineering}}, pages = {{125--143}}, publisher = {{Springer}}, title = {{{Developing the Requirements of a PLM/ALM Integration: An Industrial Case Study}}}, doi = {{10.1007/978-3-030-16134-7_11}}, year = {{2019}}, } @misc{12798, abstract = {{The digitization of the industry requires smart products and services. Smart products are mechatronic products with an increasing amount of software. To get high quality smart products to the market quickly, manufacturers need to reshape their product lifecycle processes. They need to apply system engineering-based methods to enable smooth cross-domain developments with a special focus on the software domain. One significant challenge faced by manufacturers is the harmonization of product lifecycle management (PLM), which addresses the hardware lifecycle, with application lifecycle management (ALM), which addresses the software lifecycle. To support manufacturers in this challenging activity, this paper demonstrates a proven process for developing use cases and requirements associated with a PLM/ALM integration. This process has been elicited during an industrial case study in a manufacturing company. This paper explains this process in detail. A generally applicable approach for developing the requirements of a PLM/ALM integration is extracted by removing the company-specific factors. }}, author = {{Deuter, Andreas and Otte, Andreas and Ebert, Marcel and Possel-Dölken, Frank}}, booktitle = {{4th International Conference on System-Integrated Intelligence - Intelligent, Flexible and Connected Systems in Products and Production}}, editor = {{Denkena, B. and Thoben, K. D. and Trachtler, A.}}, issn = {{2351-9789}}, keywords = {{Product lifecycle management, Application Lifecycle Management, Smart products, Systems engineering}}, location = {{Hannover}}, pages = {{107--113}}, publisher = {{Elsevier BV}}, title = {{{Developing the Requirements of a PLM/ALM Integration: An Industrial Case Study}}}, doi = {{10.1016/j.promfg.2018.06.020}}, volume = {{24}}, year = {{2018}}, } @inproceedings{574, abstract = {{The increasing industrial digitization is the driver for the fast emergence of many industrial smart products. To stay competitive, the manufacturing companies of these smart products need to optimize their internal lifecycleprocesses. Mainly, they have to converge the software and hardware lifecycleprocesses. However, even if this strategic necessity has been recognized, manufacturing companies struggle to develop and implement a roadmap of such convergence.Starting point for the realization of harmonized lifecycle processes are processmodels describing process activities and the underlying data models. This research addresses the latter one and aims to create a generic lifecycle data model. The research team created and evaluated such data model referring to development artifacts such as requirements, parts or test cases and to lifecycle artifacts such as revisions, versions and baselines. The generic lifecycle management model was evaluated by a practical development of a smart product. By this, the research provides a valuable result to maintain and increase the competitiveness of manufacturing companies.}}, author = {{Deuter, Andreas and Otte, Andreas and Ebert, Marcel}}, booktitle = {{Production Engineering and Management}}, editor = {{Padoano, Elio and Villmer, Franz-Josef}}, isbn = {{978-3-946856-01-6}}, keywords = {{PLM, ALM, Systems Engineering, VDI guideline 2206}}, location = {{Pordenone, Italy}}, number = {{1}}, pages = {{115--125}}, title = {{{Extending the Sliced V-Model to Smart Product Development}}}, year = {{2017}}, } @inproceedings{610, author = {{Deuter, Andreas and Otte, Andreas and Höllisch, Daniel}}, booktitle = {{Wissenschaftsforum Intelligente Technische Systeme (WInTeSys) 2017}}, editor = {{Trächtler, Ansgar}}, location = {{Paderborn}}, pages = {{211--222}}, title = {{{Methodisches Vorgehen zur Entwicklung und Evaluierung von Anwendungsfällen für die PLM/ALM-Integration}}}, volume = {{369}}, year = {{2017}}, } @inproceedings{594, abstract = {{Due to steadily increased demand for customized products, as well as their enhanced complexity and shorter product lifecycles, companies in all industries require a reliable prediction of the expected product development costs from the very start of product realization. Incorrectly estimated project costs may lead to serious consequences in the course of a development project. For example, offers are most often based on such early cost estimations and consequently, a major safety margin has to be added, which may result in the refusal of an order. A too low estimation of the costs of aproduct development project, on the other hand, may result in a loss for the project.In this paper, a software tool is presented for the prediction of product development costs which offers the user the ability to create a more accurate prediction of project costs on the basis of a minimum of retrograde project information. By combining a parametric cost model and cost result with stochastic character, based on the Monte Carlo method, in one software system, it is possible to significantly improve projectcost estimations.}}, author = {{Otte, Andreas and Scheideler, Eva and Villmer, Franz-Josef}}, booktitle = {{Department of Production Engineering and Management}}, editor = {{Villmer, Franz-Josef and Padoano, Elio}}, isbn = {{978-3-946856-00-9}}, keywords = {{Cost prediction, Product realization projects, Monte Carlo method, Parametric cost model, Software tool}}, location = {{Lemgo}}, number = {{1}}, pages = {{281--292}}, title = {{{Project Cost Estimator - A Parameter-Based Tool to Predict Product Realization Costs at a Very Early Stage}}}, year = {{2016}}, }