Model of PGE – Product Generation Engineering by the Example of Autonomous Driving

Abstract

Automotive product development is undergoing significant change: Autonomous driving is leading to altered customer needs that are decisive for competition and which established automotive OEMs must anticipate and systematically reflect in future product generations. To structure the provider side and manage product complexity, politics and industry, for example, classified autonomous driving into five levels (cf. Norm SAE J3016-2018) based on customer and user benefits. In order to counteract a complexity-induced "cost explosion", the functional implementation of autonomous driving must be planned across a provider’s product portfolio. For the successful implementation of such development activities, methods and processes (e.g. "functional kit") must be developed to support the product developer. The model of PGE – Product Generation Engineering according to Albers et al. describes every form of product development and enables the research and development of transferable methods. In this paper, a procedure model is developed based on the model of PGE for the systematic realization of requirements with severe effects on product complexity (e.g. redundant vehicle electrical systems, new E/E architectures) using the example of autonomous driving. The focus lies on the variation types at different product model views as well as the product function roadmap from which the functional product concept for future product generations can be derived on the basis of defined systems of objectives across the product portfolio. The procedure model aims to support the overarching planning of variations of physical subsystems by means of the functional product concept. The evaluation confirms a contribution to more efficient, customer-centric and cost-optimized product development through processes and methods of the model of PGE.

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 — 12 citations exist upstream.

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