Engineering:Modular Product Architecture
A Modular Product Architecture is a product design practice, using principles of modularity. In short, a Modular Product Architecture can be defined as a collection of modules with unique functions and strategies, protected by interfaces to deliver an evolving family of market-driven products.
Karl Ulrich, Professor in Mechanical Engineering, defines a Product Architecture as “(1) the arrangement of functional elements; (2) the mapping from functional elements to physical components; (3) the specification of the interfaces among interacting physical components”.[1] A Modular Product Architecture consists of interchangeable building blocks (modules) that can be combined into a variety of product variants.[2]
Assigning strategic intent to each module enables the producing company to connect its business objectives with the design of the product:.[3][2] This can be done by the use of Module Drivers.[3][2] The Module Drivers were first defined in 1998 by Gunnar Erixon, PhD in Design Engineering at KTH Royal Institute of Technology, and grouped into Primary and Secondary Module Drivers.[4] The Primary drivers defines the strategy of the module based on its need for development or variance, as follows[3][4]
- Carry Over: Describes a part that is unlikely to undergo any design changes during the life of the Modular Product Architecture.
- Common Unit: Describes a part that can be used for the entire product assortment or large parts of it.
- Technical Specification: Describes a part that carries the product's variance and performance properties.
- Styling: Describes visible parts of the product that represent identity towards the customer. These parts are strongly influenced by trends and are often connected to a brand or trademark.
- Technology Push: Describes a part that is likely to undergo design changes due to changing demands or technology shifts.
- Planned Development: Describes a part that the company intends to further develop, for example to better fulfill a customer value or to cut cost. The planned changes are described in the Modular Product Architecture development plan.
Using standardized interfaces between the modules enables interchangeability of different variants of modules and ensures that the Modular Product Architecture can be maintained over time.[3][5] This enables the producing company to continuously update and improve the Modular Product Architecture and respond to changing needs in the market.
Modular Product Architectures can be developed by the use of Modular function deployment.[4]
References
- ↑ Ulrich, Karl (1995-05-01). "The role of product architecture in the manufacturing firm" (in en). Research Policy 24 (3): 419–440. doi:10.1016/0048-7333(94)00775-3. ISSN 0048-7333. https://dx.doi.org/10.1016%2F0048-7333%2894%2900775-3.
- ↑ 2.0 2.1 2.2 Lehtonen, T. (2007) (in en). Designing modular product architecture in the new product development. Tampere University of Technology. ISBN 978-952-15-1898-0. https://trepo.tuni.fi/handle/10024/114367.
- ↑ 3.0 3.1 3.2 3.3 Lange, Mark; Imsdahl, Andrea (2014), Modular Function Deployment : Using Module Drivers to Impart Strategies to a Product Architecture, Springer-Verlag New York, pp. 91–118, http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-129191, retrieved 2021-03-09
- ↑ 4.0 4.1 4.2 Erixon, Gunnar (1998). Modular function deployment. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-2619.
- ↑ Gimbringer, Linnea; Svensson, Caroline (2017). Strategic Reasons for ModularizationImplications of having a modular product architecture. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-224204.
 |  |
