Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Design for X
open-in-new
<h2 id="rules-guidelines-and-methodologies-along-the-product-life-cycle">Rules, guidelines, and methodologies along the product life cycle</h2> <p>DfX methodologies address different issues that may occur in one or more phase of a <a href="/facts/Product_life_cycle_(engineering)/G3U6gtBv">product life cycle</a>: </p> <ul><li>Development phase</li> <li>Production phase</li> <li>Use phase</li> <li>Disposal phase</li></ul> <p>Each phase is explained with two dichotomous categories of tangible products to show differences in prioritizing design issues in certain <a href="/facts/Product_life_cycle_(engineering)/G3U6gtBv">product life cycle</a> phases: </p> <ul><li><a href="/facts/Consumer_durables/u3QvzW47">Consumer durables</a></li> <li><a href="/facts/Capital_goods/q963JE0C">Capital goods</a></li></ul> <p>Non-durables that are consumed physically when used, e.g. chocolate or lubricants, are not discussed. There also exist a wide range of other classifications because products are either (a) goods, (b) service, or (c) both (see OECD and Eurostat, 2005:48). Thus, one can also refer to <a href="/facts/Whole_product/vovdJxX9">whole product</a>, augmented product, or extended product. Also the business unit <a href="/facts/Strategy/vnQ3kcLw">strategy</a> of a firm are ignored, even though it significantly influences priority-setting in design. </p> <h3>Development phase</h3> <ul><li>Design rules <ul><li>Basic rules of embodiment design: clarity, <a href="/facts/Simplicity/FydqnHv6">simplicity</a>, <a href="/facts/Safety/jyH5HLSg">safety</a> (Pahl and Beitz, 1996: 205–236)</li></ul></li> <li>Organizational process <ul><li>Design for short <a href="/facts/Time_to_market/zfJzIQBN">time to market</a> (Bralla, 1996: 255–266)</li></ul></li> <li>System design, testing & validation <ul><li>Design for reliability (Bralla, 1996: 165–181), Synonyms: <a href="/facts/Reliability_engineering/cd6AS5w3">reliability engineering</a> (VDI4001-4010)</li> <li><a href="/facts/Design_for_test/wGKySXgc">Design for test</a></li> <li>Design for safety (Bralla, 1996: 195–210; VDI2244); Synonyms: <a href="/facts/Safety_engineering/ywUBoqda">safety engineering</a>, <a href="/facts/Safe-life_design/X4woW3by">safe-life design</a></li> <li>Design for quality (Bralla, 1996: 149–164; VDI2247), Synonyms: <a href="/facts/Quality_engineering/wvQ9dX8f">quality engineering</a></li> <li>Design against <a href="/facts/Corrosion/lIC7H4we">corrosion</a> damage (Pahl and Beitz, 1996: 294–304)</li> <li>Design for minimum <a href="/facts/Risk/tbBEDA0V">risk</a> (Pahl and Beitz, 1996:373–380)</li></ul></li></ul> <h3>Production-operations phase</h3> <ul><li>Design rules <ul><li><a href="/facts/Design_to_cost/rVvxt4pF">Design to cost</a> (Pahl and Beitz, 1996: 467–494; VDI2234; VDI 2235), see <a href="/facts/Target_costing/Kcp95EzT">Target costing</a>, <a href="/facts/Value_engineering/sd7jPdCt">Value engineering</a></li> <li>Design to standards (Pahl and Beitz, 1996:349–356), see <a href="/facts/Interchangeable_parts/wRgReIGV">Interchangeable parts</a>, product modularity, product architecture, product platform</li></ul></li> <li>Design Guidelines <ul><li><a href="/facts/Design_for_assembly/RkbonJJ8">Design for assembly</a> (Bralla, 1996: 127–136), (Pahl and Beitz, 1996: 340–349)</li> <li><a href="/facts/Design_for_inspection/u1jjP52C">Design for inspection</a> (Hitchens Carl (2014) Guide to Engineering Metrology)</li> <li><a href="/facts/Design_for_manufacturability/mujLQqYz">Design for manufacturability</a> (Bralla, 1996: 137–148), (Pahl and Beitz, 1996: 317–340)</li> <li><a href="/facts/Design_for_logistics/76A3nHfV">Design for logistics</a>, design for postponement (see <a href="/facts/Delayed_differentiation/2k8kS8D8">Delayed differentiation</a>)</li></ul></li> <li>Specific situations <ul><li>Design for electronic assemblies (Bralla, 1996: 267–279)</li> <li>Design for low-quantity production (Bralla, 1996: 280–288)</li></ul></li></ul> <h4>Design rules</h4> <p><a href="/facts/Design_to_cost/rVvxt4pF">Design to cost</a> and design to standards serves <a href="/facts/Cost_reduction/hqbQbchh">cost reduction</a> in production operations, or respectively supply chain operations. Except for luxury goods or brands (e.g., <a href="/facts/Swarovski/CNN9atIs">Swarovski</a> crystals, <a href="/facts/Haute_couture/MDkf5hAR">Haute couture</a> fashion, etc.), most goods, even exclusive products, rely on <a href="/facts/Cost_reduction/hqbQbchh">cost reduction</a>, if these are <a href="/facts/Mass_produced/31Cmgjuc">mass produced</a>. The same is valid for the functional production strategy of <a href="/facts/Mass_customization/UWu7jQ69">mass customization</a>. Through <a href="/facts/Engineering_design/heCF3wFo">engineering design</a> physical interfaces between a) parts or components or assemblies of the product and b) the manufacturing equipment and the logistical material flow systems can be changed, and thus cost reducing effects in operating the latter may be achieved. </p> <h4>Design guidelines</h4> <ul><li><a href="/facts/Design_for_manufacturability/mujLQqYz">Design for manufacturability</a> ensures the fabrication of single parts or components that are based on an integral design in mechanical engineering terms. Every production technology has its own specific design guideline that needs to be consulted depending on the situation.</li> <li><a href="/facts/Design_for_assembly/RkbonJJ8">Design for assembly</a> addresses the combination of single parts or components to subassemblies, assemblies, modules, systems, etc., that are based on a differential design in mechanical engineering terms. An important issue is how the embodied interfaces within a product are designed (mechanical engineering, electrical engineering). Contrary, software or respectively firmware interfaces (software engineering, electrical engineering) are not significant for assembly operations, because these can be easily flash installed within one production step. That is a cost efficient way to enable a wide range of product variants.</li> <li><a href="/facts/Design_for_logistics/76A3nHfV">Design for logistics</a> covers issues along supply chain partners (i.e., legally independent firms) but is by its means closely related to the <a href="/facts/Design_for_assembly/RkbonJJ8">design for assembly</a> guidelines. In academic research, <a href="/facts/Design_for_logistics/76A3nHfV">design for logistics</a> is tangent to the <a href="/facts/Strategic_alliance/CPQl6gbY">strategic alliances</a>, <a href="/facts/Supply_chain_management/3bEP00vC">supply chain management</a>, and the <a href="/facts/Engineering/RFVg8H3I">engineering</a> part of <a href="/facts/New_product_development/ogcXTIco">new product development</a>. For example, Sanchez and Mahoney (1996) argued that product <a href="/facts/Modularity/mptqhanB">modularity</a> (i.e., how physical sub-systems of a product are sub-divided through interfaces; also called product or system architecture), and organizational <a href="/facts/Modularity/mptqhanB">modularity</a> (i.e., how organisational entities are structured), depend on each other. Fixson <i>et al</i>. (2005) found that the relationship between product architecture and organisational structure is reciprocal in the contexts of <a href="/facts/Early_supplier_involvement/ogcXTIco">early supplier involvement</a> during <a href="/facts/System_design/hFWYoaNP">system design</a> and the <a href="/facts/Concept_phase/G3U6gtBv">concept phase</a> of the product development process.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a></li></ul> <h3>Use phase</h3> <ul><li>User focused, see <a href="/facts/Product_design/Fjwu9wLq">Product design</a>, <a href="/facts/Industrial_design/6oBprKds">Industrial design</a> <ul><li>Design for user-friendliness (Bralla, 1996: 237–254), see <a href="/facts/Usability/zuAnqu9Q">Usability</a>, <a href="/facts/Ben_Shneiderman/y6JH0pFh">Ben Shneiderman</a>, <a href="/facts/Emotional_Design/w0d0mGeD">Emotional Design</a></li> <li>Design for <a href="/facts/Ergonomics/prAcGtDW">ergonomics</a> (Pahl and Beitz, 1996: 305–310)</li> <li>Design for <a href="/facts/Aesthetics/FSD8f7oF">aesthetics</a> (Pahl and Beitz, 1996: 311–316)</li></ul></li> <li>After-sales focused <ul><li>Design for <a href="/facts/Serviceability_(computer)/w9nQfmJF">serviceability</a> (Bralla, 1996: 182–194; Pahl and Beitz, 1996: 357–359),</li> <li>Design for <a href="/facts/Maintainability/SmyLaINQ">maintainability</a> (Bralla, 1996: 182–194; Pahl and Beitz, 1996: 357–359; VDI2246),</li></ul></li> <li>Design for repair-reuse-recyclability, a key part of the <a href="/facts/International_Design_Excellence_Awards/udKA0mRM">International Design Excellence Awards</a> criteria</li></ul> <h4>Comparison: consumer durables vs. capital goods</h4> <p>User focused design guidelines may be associated with <a href="/facts/Consumer_durables/u3QvzW47">consumer durables</a>, and after-sales focused design guidelines may be more important for <a href="/facts/Capital_goods/q963JE0C">capital goods</a>. However, in case of capital goods design for <a href="/facts/Ergonomics/prAcGtDW">ergonomics</a> is needed to ensure clarity, <a href="/facts/Simplicity/FydqnHv6">simplicity</a>, and <a href="/facts/Safety/jyH5HLSg">safety</a> between the human-machine interface. The intent is to avoid shop-accidents as well as to ensure efficient work flows. Also design for <a href="/facts/Aesthetics/FSD8f7oF">aesthetics</a> has become more and more important for capital goods in recent years. In <a href="/facts/Business-to-business/9vKUQSmL">business-to-business</a> (B2B) markets, capital goods are usually ordered, or respectively business transaction are initiated, at industrial trade fairs. The functional traits of capital goods in technical terms are assumed generally as fulfilled across all exhibiting competitors. Therefore, a purchaser may be subliminally influenced by the aesthetics of a <a href="/facts/Capital_good/q963JE0C">capital good</a> when it comes to a purchasing decision. For consumer durables the aspect of after sales highly depends on the business unit's strategy in terms of service offerings, therefore generally statements are not possible to formulate. </p> <h3>Disposal phase</h3> <ul><li><a href="/facts/Design_for_Environment/XCRHBbkw">Design for Environment</a> (Bralla, 1996: 182–194), see also <a href="/facts/Life_cycle_assessment/vGKCvfYf">Life cycle assessment</a>, <a href="/facts/Technology_assessment/7TIxr6Tu">Technology assessment</a>, <a href="/facts/Sustainable_engineering/SgxlfPtG">sustainable engineering</a>, <a href="/facts/Sustainable_design/szkYtSf2">sustainable design</a></li> <li>Design for <a href="/facts/Recycling/x9X7GAzz">recycling</a> (Pahl and Beitz, 1996: 360–372), design for disassembly <ul><li><a href="/facts/Active_disassembly/1dohLIUG">Active disassembly</a></li> <li><a href="/facts/Remanufacturing/QS85dlNX">Remanufacturing</a></li> <li>Recycling of electrical and electronical equipment – Disassembly and processing (VDI2343)</li> <li>Recycling oriented product development (VDI 2243)</li></ul></li></ul> <h2 id="similar-concepts-in-product-development">Similar concepts in product development</h2> <p>Several other concepts in product development and new product development are very closely related: </p> <ul><li><i>Engineering Design:</i> Design for X</li> <li><i>Time dimension</i>: <a href="/facts/Product_lifecycle_(engineering)/G3U6gtBv">product life cycle</a>, <a href="/facts/Product_life_cycle_engineering/G3U6gtBv">Product Life Cycle Engineering</a>, <a href="/facts/Product_life-cycle_management/G3U6gtBv">product life cycle management</a> (that is not the same like the <a href="/facts/Product_cycle/G3U6gtBv">product cycle</a> in <a href="/facts/Business/For1e8Nh">business</a> studies and <a href="/facts/Economics/HYctA2Dn">economics</a>, see e.g. Vernon (1966)). Primarily, the unit of analysis here is <i>a product</i>, or more clearly, one item</li> <li><i>Meso-level organisation</i>: <a href="/facts/Concurrent_engineering/2k5rFINN">concurrent engineering</a> (American), simultaneous engineering (British), and overlapping-parallel product development processes</li> <li><i>Micro-level organisation</i>: <a href="/facts/Cross-functional_team/XghkMdXS">cross-functional teams</a>, inter-disciplinary teams, etc.</li></ul> <p>Looking at all life stages of a product (<a href="/facts/Product_life_cycle_(engineering)/G3U6gtBv">product life cycle (engineering)</a>) is essential for design for X, otherwise the <i>X</i> may be suboptimized, or make no sense. When asking what competencies are required for analysing situations that may occur along the life of a product, it becomes clear that several departmental functions are required. An historical assumption is that <a href="/facts/New_product_development/ogcXTIco">new product development</a> is conducted in a departmental-stage process (that can be traced back to the classical <a href="/facts/Theory_of_the_firm/DpedvDuh">theory of the firm</a>, e.g. <a href="/facts/Max_Weber/MF3HU6bN">Max Weber</a>'s bureaucracy or <a href="/facts/Henri_Fayol/0qap0Wx4">Henri Fayol</a>'s administration principles), i.e., new product development activities are closely associated with certain department of a firm. At the start of the 1990s, the concept of <a href="/facts/Concurrent_engineering/2k5rFINN">concurrent engineering</a> gained popularity to overcome dysfunctions of departmental stage processes. Concurrent engineering postulates that several departments must work closely together for certain new product development activities (see Clark and Fujimoto, 1991). The logical consequence was the emergence of the organisational mechanism of <a href="/facts/Cross-functional_team/XghkMdXS">cross-functional teams</a>. For example, Filippini <i>et al</i>. (2005) found evidence that overlapping product development processes only accelerate new product development projects if these are executed by a <a href="/facts/Cross-functional_team/XghkMdXS">cross-functional team</a>, vice versa. </p> <p>Design for X references </p> <ul><li>Pahl, G., and Beitz, W. (1996). Engineering Design - A Systematic Approach, 2nd edition, London: Springer. <a href="https://books.google.com/books?hl=en&lr=&id=8fuhesYeJmkC&oi=fnd&pg=PR15&sig=9ulWL5tPOSV2IqnXx7F6IVoKzeE&dq=Pahl+and+Beitz,+1996">(Google Books Preview)</a></li> <li>Bralla, J. G. (1996). Design for Excellence. New York: McGraw-Hill.</li> <li>VDI-guidelines of the "<a href="/facts/Verein_Deutscher_Ingenieure/7epCLHzg">Verein Deutscher Ingenieure</a>" can requested under <a href="https://web.archive.org/web/20070302232927/http://www.vdi.de/vdi/english/vrp/richtlinien/guidelines/10678/index.php">(www)</a> or purchased from the publisher Beuth <a href="http://www.beuth.de">(www)</a>; most guidelines are bilingual in German and English.</li></ul> <p>Auxiliary references </p> <ul><li>Doz, Y. and Santos, J.F.P. (1997). On the management of knowledge: from the transparency of collocation and co-setting to the quandary of dispersion and differentiation. Fontainebleau, France.</li> <li>Sanchez, R. and Mahoney, J.T. (1996) Modularity, flexibility, and knowledge management in product and organization design. Strategic Management Journal, 17, 63–76.</li> <li>OECD; Eurostat (2005). Oslo Manual 2005: The Measurement of Scientific and Technological Activities - Proposed guidelines for collecting and interpreting technological innovation data. Organisation for Economic Co-operation and Development, Statistical Office of the European Communities. <a href="https://web.archive.org/web/20061017173113/http://epp.eurostat.ec.europa.eu/cache/ITY_PUBLIC/OSLO/EN/OSLO-EN.PDF">(pdf)</a></li> <li>Vernon, R. (1966) International Investment and International Trade in the Product Cycle. The Quarterly Journal of Economics, 80, 190–207.</li> <li>Clark, K.B. and Fujimoto, T. (1991). Product development performance. Boston, Massachusetts: Harvard Business School Press.</li> <li>Filippini, R., Salmaso, L. and Tessarolo, P. (2005) Product Development Time Performance: Investigating the Effect of Interactions between Drivers. Journal of Product Innovation Management, 21, 199–214.</li></ul> <h2 id="external-links">External links</h2> Wikimedia Commons has media related to Design for X. <ul><li><a href="http://www.dfx-symposium.de/">DfX-Symposium in Germany</a></li> <li><a href="https://web.archive.org/web/20060621104722/http://bits.me.berkeley.edu/mmcs/PROPRNT2/WELCOME.HTM">The IBM Proprinter: A Case Study in Engineering Design</a></li> <li>Mottonen, M., Harkonen, J., Belt, P., Haapasalo, H. and Simila, J. (2009). <a href="https://www.researchgate.net/publication/220672654_Managerial_view_on_design_for_manufacturing">"Managerial view on design for manufacturing"</a>, <i>Industrial Management & Data Systems</i>, Vol. 109, No. 6, pp. 859–872.</li> <li><a href="https://archive.today/20130122021435/http://www.emeraldinsight.com/Insight/viewContentItem.do;jsessionid=E776EAF1CEA5579AD6D4E5DCFF5117B6?contentType=Article&contentId=1798672">[1]</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Andrew B. Kahng, DfX and Signoff: The Coming Challenges and Opportunities, Keynote Address, IEEE Computer Society Annual Symposium on VLSI (ISVLSI), 2012. <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Saraju Mohanty, DFX for Nanoelectronic Embedded Systems, Keynote Address at First IEEE Sponsored International Conference on Control, Automation, Robotics and Embedded System, CARE-2013, http://care.iiitdmj.ac.in/Keynote_Speakers.html Archived 2013-10-09 at the Wayback Machine <a href="/wiki/Saraju_Mohanty" target="_blank">/wiki/Saraju_Mohanty</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>The DfX concept, http://www.ami.ac.uk/courses/topics/0248_dfx/ Archived 2014-07-06 at the Wayback Machine <a href="http://www.ami.ac.uk/courses/topics/0248_dfx/" target="_blank">http://www.ami.ac.uk/courses/topics/0248_dfx/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"DFA Transforms Computer Chassis". <a href="http://www.assemblymag.com/articles/84261-dfa-transforms-computer-chassis" target="_blank">http://www.assemblymag.com/articles/84261-dfa-transforms-computer-chassis</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Saraju Mohanty, Chapter 3 Nanoelectronics Issues in Design for excellence, "Nanoelectronic Mixed-Signal System Design", ISBN 978-0071825719 and 0071825711, 1st Edition, McGraw-Hill, 2015. <a href="/wiki/Saraju_Mohanty" target="_blank">/wiki/Saraju_Mohanty</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Fixson, S. K., Ro, Y., & Liker, J. K. (2005). "Modularization and Outsourcing: Who drives whom? - A Study of Generational Sequences in the U.S. Automotive Cockpit Industry", International Journal of Automotive Technology and Management, 5(2): 166–183 <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> </ol>