Modular function deployment: Difference between revisions

Revision as of 23:27, 13 August 2018

Revision as of 14:39, 2 January 2019

Line 4:

}}

'''[https://modularmanagement.com/mfd/ Modular functionFunction deploymentDeployment (MFD)])''' is a systematic method andinvented procedure forby [[company]https://modularmanagement.com/ Modular Management]-supportive to create product [[modularization]]architectures.

With a modular product architecture, companies can offer a wide range of products and services without increasing complexity, since modules and module variants, like LEGO pieces, can be configured in many different ways. The MFD process ensures that each module has functional, strategic and customer-centric value and can be combined with other modules through standardized interfaces. A modular product architecture is a means to enable [[Mass_customization|mass customization]], where customers configure and order personalized - rather than ready-made - products and services.

==Five steps==

MFD consists of five major steps. It starts with [[quality function deployment]] (QFD) analysis to establish [[customer]] requirements and identify important design requirements with a special emphasis on [[modularity]]. [[Functional requirement|Functionality requirements]] for the product are analyzed, and technical solutions are selected. This is followed by systematic generation and selection of modular concepts, in which the module indication matrix (MIM) is used to identify possible [[modular design|modules]] by examining the interrelationships between "module drivers" and technical solutions.

==Five stepsSteps==

MIM also provides a mechanism for investigating opportunities of integrating multiple functions into single modules. The expected effects of the redesign can be estimated, and an evaluation can be carried out for each modular concept. The MIM is then re-used to identify opportunities for further improvements to the single modules.{{Citation needed|date=July 2018}}

MFD consists of five steps:

1. Clarify Customer Needs

2. Identify Functions and Solutions

3. Propose Modules and Interfaces

4. Define Variants and Configurations

5. Confirm Architecture Feasibility

== References ==