Design for X

Last updated

Design for excellence (DfX or DFX) is a term and abbreviation used interchangeably in the existing literature, [1] [2] [3] where the X in design for X is a variable which can have one of many possible values. [4] In many fields (e.g., very-large-scale integration (VLSI) and nanoelectronics) X may represent several traits or features including: manufacturability, power, variability, cost, yield, or reliability. [5] This gives rise to the terms design for manufacturability (DfM, DFM), design for inspection (DFI), design for variability (DfV), design for cost (DfC). Similarly, other disciplines may associate other traits, attributes, or objectives for X.

Contents

Under the label design for X, a wide set of specific design guidelines are summarized. Each design guideline addresses a given issue that is caused by, or affects the traits of, a product. The design guidelines usually propose an approach and corresponding methods that may help to generate and apply technical knowledge to control, improve, or even invent particular traits of a product. From a knowledge-based view, the design guideline represents an explicit form of knowledge, that contains information about knowing-how-to (see Procedural knowledge). However, two problems are prevalent. First, this explicit knowledge (i.e., the design guidelines) were transformed from a tacit form of knowledge (i.e., by experienced engineers, or other specialists). Thus, it is not granted that a freshman or someone who is outside the subject area will comprehend this generated explicit knowledge. This is because it still contains embedded fractions of knowledge or respectively include non-obvious assumptions, also called context-dependency (see e.g. Doz and Santos, 1997:16–18). Second, the traits of a product are likely to exceed the knowledge base of one human. There exists a wide range of specialized fields of engineering, and considering the whole life cycle of a product will require non-engineering expertise. For this purpose, examples of design guidelines are listed in the following.

Rules, guidelines, and methodologies along the product life cycle

DfX methodologies address different issues that may occur in one or more phase of a product life cycle:

Each phase is explained with two dichotomous categories of tangible products to show differences in prioritizing design issues in certain product life cycle phases:

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 whole product, augmented product, or extended product. Also the business unit strategy of a firm are ignored, even though it significantly influences priority-setting in design.

Development phase

Production-operations phase

Design rules

Design to cost and design to standards serves cost reduction in production operations, or respectively supply chain operations. Except for luxury goods or brands (e.g., Swarovski crystals, Haute couture fashion, etc.), most goods, even exclusive products, rely on cost reduction, if these are mass produced. The same is valid for the functional production strategy of mass customization. Through engineering design 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.

Design guidelines

  • Design for manufacturability 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.
  • Design for assembly 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.
  • Design for logistics covers issues along supply chain partners (i.e., legally independent firms) but is by its means closely related to the design for assembly guidelines. In academic research, design for logistics is tangent to the strategic alliances, supply chain management, and the engineering part of new product development. For example, Sanchez and Mahoney (1996) argued that product modularity (i.e., how physical sub-systems of a product are sub-divided through interfaces; also called product or system architecture), and organizational modularity (i.e., how organisational entities are structured), depend on each other, and Fixson et al. (2005) found that the relationship between product architecture and organisational structure is reciprocal in context of early supplier involvement (ESI) during the system design or respectively concept phase of the product development process.

Use phase

Comparison: consumer durables vs. capital goods

User focused design guidelines may be associated with consumer durables, and after-sales focused design guidelines may be more important for capital goods. However, in case of capital goods design for ergonomics is needed to ensure clarity, simplicity, and safety between the human-machine interface. The intent is to avoid shop-accidents as well as to ensure efficient work flows. Also design for aesthetics has become more and more important for capital goods in recent years. In business-to-business (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 capital good 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.

Disposal phase

Similar concepts in product development

Several other concepts in product development and new product development are very closely related:

Looking at all life stages of a product (product life cycle (engineering)) is essential for design for X, otherwise the X 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 new product development is conducted in a departmental-stage process (that can be traced back to the classical theory of the firm, e.g. Max Weber's bureaucracy or Henri Fayol'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 concurrent engineering 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 cross-functional teams. For example, Filippini et al. (2005) found evidence that overlapping product development processes only accelerate new product development projects if these are executed by a cross-functional team, vice versa.

Related Research Articles

<span class="mw-page-title-main">Design</span> Plan for the construction of an object or system

A design is a concept of either an object, a process, or a system that is specific and, in most cases, detailed. Design refers to something that is or has been intentionally created by a thinking agent, though it is sometimes used to refer to the nature of something. The verb to design expresses the process of developing a design. In some cases, the direct construction of an object without an explicit prior plan may also be considered to be a design. The design usually has to satisfy certain goals and constraints; may take into account aesthetic, functional, economic, or socio-political considerations; and is expected to interact with a certain environment. Typical examples of designs include architectural and engineering drawings, circuit diagrams, sewing patterns and less tangible artefacts such as business process models.

<span class="mw-page-title-main">Systems engineering</span> Interdisciplinary field of engineering

Systems engineering is an interdisciplinary field of engineering and engineering management that focuses on how to design, integrate, and manage complex systems over their life cycles. At its core, systems engineering utilizes systems thinking principles to organize this body of knowledge. The individual outcome of such efforts, an engineered system, can be defined as a combination of components that work in synergy to collectively perform a useful function.

In business and engineering, product development or new product development covers the complete process of bringing a new product to market, renewing an existing product and introducing a product in a new market. A central aspect of NPD is product design, along with various business considerations. New product development is described broadly as the transformation of a market opportunity into a product available for sale. The products developed by an organisation provide the means for it to generate income. For many technology-intensive firms their approach is based on exploiting technological innovation in a rapidly changing market.

Rapid application development (RAD), also called rapid application building (RAB), is both a general term for adaptive software development approaches, and the name for James Martin's method of rapid development. In general, RAD approaches to software development put less emphasis on planning and more emphasis on an adaptive process. Prototypes are often used in addition to or sometimes even instead of design specifications.

The following outline is provided as an overview of and topical guide to software engineering:

In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder. Requirements can come with different levels of specificity; for example, a requirement specification or requirement "spec" refers to an explicit, highly objective/clear requirement to be satisfied by a material, design, product, or service.

<span class="mw-page-title-main">Systems development life cycle</span> Systems engineering terms

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.

<span class="mw-page-title-main">Product lifecycle</span> Duration of processing of products from inception, to engineering, design & manufacture

In industry, product lifecycle management (PLM) is the process of managing the entire lifecycle of a product from its inception through the engineering, design and manufacture, as well as the service and disposal of manufactured products. PLM integrates people, data, processes, and business systems and provides a product information backbone for companies and their extended enterprises.

<span class="mw-page-title-main">Life-cycle assessment</span> Methodology for assessing environmental impacts

Life cycle assessment or LCA is a methodology for assessing environmental impacts associated with all the stages of the life cycle of a commercial product, process, or service. For instance, in the case of a manufactured product, environmental impacts are assessed from raw material extraction and processing (cradle), through the product's manufacture, distribution and use, to the recycling or final disposal of the materials composing it (grave).

In software development, code reuse, also called software reuse, is the use of existing software, or software knowledge, to build new software, following the reusability principles.

<span class="mw-page-title-main">Bill of materials</span> List used in manufacturing

A bill of materials or product structure is a list of the raw materials, sub-assemblies, intermediate assemblies, sub-components, parts, and the quantities of each needed to manufacture an end product. A BOM may be used for communication between manufacturing partners or confined to a single manufacturing plant. A bill of materials is often tied to a production order whose issuance may generate reservations for components in the bill of materials that are in stock and requisitions for components that are not in stock.

<span class="mw-page-title-main">Computer-aided production engineering</span>

Computer-aided production engineering (CAPE) is a relatively new and significant branch of engineering. Global manufacturing has changed the environment in which goods are produced. Meanwhile, the rapid development of electronics and communication technologies has required design and manufacturing to keep pace.

Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome should conform.

<span class="mw-page-title-main">Modular design</span> Design approach

Modular design, or modularity in design, is a design principle that subdivides a system into smaller parts called modules, which can be independently created, modified, replaced, or exchanged with other modules or between different systems.

Design methods are procedures, techniques, aids, or tools for designing. They offer a number of different kinds of activities that a designer might use within an overall design process. Conventional procedures of design, such as drawing, can be regarded as design methods, but since the 1950s new procedures have been developed that are more usually grouped together under the name of "design methods". What design methods have in common is that they "are attempts to make public the hitherto private thinking of designers; to externalise the design process".

Design for the Environment (DfE) is a design approach to reduce the overall human health and environmental impact of a product, process or service, where impacts are considered across its life cycle. Different software tools have been developed to assist designers in finding optimized products or processes/services. DfE is also the original name of a United States Environmental Protection Agency (EPA) program, created in 1992, that works to prevent pollution, and the risk pollution presents to humans and the environment. The program provides information regarding safer chemical formulations for cleaning and other products. EPA renamed its program "Safer Choice" in 2015.

<span class="mw-page-title-main">V-model (software development)</span> Software development methodology

In software development, the V-model represents a development process that may be considered an extension of the waterfall model, and is an example of the more general V-model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing. The horizontal and vertical axes represent time or project completeness (left-to-right) and level of abstraction, respectively.

<span class="mw-page-title-main">Sustainable engineering</span> Engineering discipline

Sustainable engineering is the process of designing or operating systems such that they use energy and resources sustainably, in other words, at a rate that does not compromise the natural environment, or the ability of future generations to meet their own needs.

In software engineering, a software development process is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. It is also known as a software development life cycle (SDLC). The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

Design for All in the context of information and communications technology (ICT) is the conscious and systematic effort to proactively apply principles, methods and tools to promote universal design in computer-related technologies, including Internet-based technologies, thus avoiding the need for a posteriori adaptations, or specialised design.

References

  1. Andrew B. Kahng, DfX and Signoff: The Coming Challenges and Opportunities, Keynote Address, IEEE Computer Society Annual Symposium on VLSI (ISVLSI), 2012.
  2. 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
  3. The DfX concept, http://www.ami.ac.uk/courses/topics/0248_dfx/ Archived 2014-07-06 at the Wayback Machine
  4. "DFA Transforms Computer Chassis".
  5. 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.

Design for X references

Auxiliary references