Assessing the cost saving potential of shared product architectures

Mortensen, Niels Henrik; Hansen, Christian Lindschou; Løkkegaard, Martin; Hvam, Lars

doi:10.1177/1063293x15624133

Cited by 15 publications

(38 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The DNA method fundamentally builds on the work done by Harlou (2006) and Mortensen et al (2016) in combination with morphology methods (Ko and Kuo, 2010; Zwicky, 1967). It is a way of modelling and challenging the total numbers of architectures in a company.…”

Section: Dna Methodsmentioning

confidence: 99%

“…Many scholars, point out that segmentation analysis and planning is a key activity when developing product architectures, especially in the beginning of the process (De Weck, 2006; Meyer and Lehnerd, 1997; Mortensen et al, 2016; Otto et al, 2016). Therefore, the first stage of the DNA method is concerned with analysing the market segments and competition (Figure 1(a)).…”

Section: Dna Methodsmentioning

confidence: 99%

“…Mortensen et al (2016) developed a comprehensive framework called AME – architecture mapping and evaluation – that maps product and manufacturing architectures, links them to the market and calculates the financial impact of changing the architectures. The framework is largely based on a company’s existing product portfolio, and its main benefit is grooming existing architectures rather than changing them.…”

Section: State Of the Artmentioning

confidence: 99%

“…However, most of this research focuses on the development of single product platforms, commonality across product families, product portfolio rationalisation and so on (Dahmus et al, 2001; Hansen, 2014; Harlou, 2006). Little research has been conducted on deciding the total number of architectures for a full portfolio of products with multiple product families (Mortensen et al, 2016). Hence, in this article, we aim to address this gap in the research.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Deciding on the total number of product architectures

Askhøj

Mortensen

2019

Concurrent Engineering

Self Cite

View full text Add to dashboard Cite

Many industries have to deliver mass customised products rather than mass produced products in today’s markets, and companies often aim to accommodate this by introducing modular product architectures. However, today’s methods do not explicitly support the decision on how many architectures a company’s entire product programme should be based on. Therefore, this article presents a method to help companies decide on the total number of product architectures they require. The method goes through four stages: market segmentation, mapping new generation with an existing architecture strategy, architecture changes and the new architecture strategy. Essentially, the method is a way of modelling and challenging the total number of architectures in a company. The method was tested on a case company and helped it to reduce its number of architectures from 19 to 7 while at the same time introducing new product variants. Cost reductions due to a higher level of commonality were achieved and the new product architectures were prepared for future innovations.

show abstract

Section: Dna Methodsmentioning

confidence: 99%

Section: Dna Methodsmentioning

confidence: 99%

Section: State Of the Artmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Deciding on the total number of product architectures

Askhøj

Mortensen

2019

Concurrent Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Bonev et al (2013) established product requirement development model for reflecting customer needs to multi-layered architecture by combining PFMP with matrix-based methods. Other tools such as interface diagram (Bruun et al, 2015) and architecture ICED19 mapping and evaluation (AME; Mortensen et al, 2016) were continuously advanced to support the overall framework for product family architecture design.…”

Section: Product Family Architecture (Cross-domain Viewpoint)mentioning

confidence: 99%

A Framework for Development Architecture for Modular Products: Cross-Domain Variety Management Perspective

Oh¹,

Lim²,

Cho³

et al. 2019

Proc. Int. Conf. Eng. Des.

View full text Add to dashboard Cite

Variety management is a cross-domain issue in product family design. In the real field, the relationships across the domains are so complex for most of the existing product families that they cannot be easily identified without proper reference architecture. This reference architecture should provide the cross- domain mapping mechanisms in an explicit manner and be able to identify the proper units for management. From this perspective of cross-domain framework, this paper introduces development architecture (DA) to describe the relationships between elements in market, design, and production domains and to give insights for the cross-domain variety management in the product development stage. DA has three parts: (1) the arrangement of elements in each domain, (2) the mapping between elements, and (3) the identification of management sets and key interfaces which are the proper units for variety management. The proposed development architecture framework is applied to the case of front chassis family of modules of an automobile.

show abstract

Modular Maintenance Decision Architecture

Agergaard,

Sigsgaard,

Mortensen

et al. 2023

Proc. Des. Soc.

Self Cite

View full text Add to dashboard Cite

The operation of large production assets requires many decisions from the acquisition and design of new assets to the choice of lubricant for a specific piece of equipment. The decisions made in maintenance have a direct effect on the management of the production process, making it important to ensure correct maintenance decision making. However, studies on maintenance decision making tend to focus on smaller areas of decisions being made in a process, but rarely the entire process. To introduce more studies that consider the entire maintenance process, this paper proposes using a modular Maintenance Decision Architecture. The paper introduces a framework for structuring information sources into standardized information modules and mapping them to maintenance decisions made across the entire organization. The application of approaches from product, system, and service engineering are used to support the management of the complexities of maintenance of large production facilities.

show abstract

Assessing the cost saving potential of shared product architectures

Cited by 15 publications

References 23 publications

Deciding on the total number of product architectures

Deciding on the total number of product architectures

A Framework for Development Architecture for Modular Products: Cross-Domain Variety Management Perspective

Modular Maintenance Decision Architecture

Contact Info

Product

Resources

About