Browse Topic: Quality function deployment

Items (82)
This document provides methods and techniques for implementing a reliability program throughout the full life cycle of a software product, whether the product is considered as standalone or part of a system. This document is the companion to the Software Reliability Program Standard [JA1002]. The Standard describes the requirements of a software reliability program to define, meet, and demonstrate assurance of software product reliability using a Plan-Case framework and implemented within the context of a system application. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented by software components. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of software whose reliability is an important performance parameter. Applicability of specific practices will depend on the reliability-significance of the software, application domain, and life cycle stage of the software. Following guidelines in this document does not guarantee required reliability will be achieved, or that any certification authority will accept the results as sufficient evidence that requisite reliability has been achieved. Following guidelines in this document will provide insight into what level of reliability has been achieved. With proper customer, certification authority, and supplier negotiation and interaction in accordance with these guidelines, it is more likely that the achieved reliability will be acceptable.
G-41 Reliability
The work performed for the Adaptive Resilient Engineered Structures (ARES) program sponsored by the U.S. Army constitutes a trade study and resulting proposal for a structural demonstrator platform. The trade study was conducted using the Quality Function Deployment (QFD) process and a subsequent Artificial Intelligence (AI) exercise to find clusters of technologies for structural efficiency and resilience from Boeing's internal research activities. From a selection of approximately 150 technologies at different TRLs, Boeing subject matter experts (SMEs) for structural technologies identified several characteristics that could potentially determine the development of ARES structural demonstrator. Through the QFD process, the list of technologies was down selected about 50 unique technologies for consideration. The next stage of the QFD process entailed in identifying 37 different attributes or criteria long which each of these technologies would be assessed. They were grouped under two different categories: vehicle performance criteria and program performance criteria. Importance scores were provided by the SMEs independently and then a statistical approach for AI was used to distill them to 9 significant ones (labeled as 'Pillars') and a further distillation to 3 significant features (labeled as 'Super Metrics'). Clustering algorithms were then employed to group the set of technologies that could provide the resiliency targets sought for the demonstrator platform. The clusters were compared a hypothetical ideal platform to determine suitability and finally, 12 technologies merited attention toward the stated goals of the demonstrator platform.
Nevinsky, MichaelSircar, SaurabhMisciagna, DavidLorthridge, Derrell
The path towards clean mobility points in the direction of battery electric vehicles (BEVs) as a possible transportation solution. Despite a growing market penetration worldwide, emerging countries are struggling to successfully adopt BEV with current vehicle models. The literature presents an embracing discussion about BEV barriers but lacks into suggesting practical actions into BEV design. Based on a product development methodology and value analysis, this research aims to review factors holding back the BEV adoption in developing countries and to apply these factors into BEV features and design specifications. The literature was systematically reviewed based on the Brazilian case scenario to cast customer requirements for numerical evaluation through the Mudge Method. These were later translated into design requirements and ranked according to their relative importance with the quality function deployment (QFD). The results show that vehicle safety, pricing, and range anxiety are the most influential requirements for the customers, so the design must strongly transmit these features. Battery issues and the selling price are found in the prior design requirements, so they must be the main guidelines in decision-making and the vehicle features. Based on these findings, it has been seen that a small urban car can fulfil an urban customer necessity with the present technology state and pricing, which can help to boost the BEV acceptance and the image of a ready concept for the market.
Colpo, Leonardo R.Nora, Macklini DallaRomano, Leonardo N.Glufke, Ronaldo M.Rech, Cassiano
This paper introduces a wholistic approach for design and development of a turbo-charged four-cylinder engine system using the Quality Function Deployment (QFD) methodology for target setting. Additionally, an exhaustive comparison is conducted between the current product’s NVH performance and that of the target product to design the required countermeasures to reach the desired performance. The proposed process consists of subsequent phases; starting with the voice of customer collection and organizing customer clinic, definition of strategic target to reach, specifying the gap between the current product’s performance, and setting the desired target levels to design and develop the required enablers to close the gap. The final phase is the demonstration of the current product with emulated enablers to the stakeholders.
Farrokhzadeh, Hooman
Reliability Apportionment using Quality Function Deployment2022-26-00175/26/2022
It is important to allocate reliability goal of the system to its subsystems or components in the early design stage of the new product design and introduction project. Reliability allocation can be equal or weighted. For weighted reliability allocation the weighing factors are required for corresponding failure modes or subsystems or components. Currently, these weighing factors are determined using FMEA (Failure Mode and Effect Analysis) method, Engineering Judgement method or Expert Opinion method. An implementation of these methods takes longer time and efforts to converge the allocation output; because the input parameters to these tools are definitive of functional and physical domain of the system, which typically gets evolved, matured and finalized at the later stage of a product definition phase. Also, in certain cases deployment of these methods are prone to immature inputs causing rework and lack physics of failure analysis for life performance. These aspects of current methods make the implementation a lengthier and iterative process to converge reliability apportionment, which affects the development schedule, resource expenditure and time to market. In this paper, a comprehensive approach is proposed, which leverages QFD (Quality Functional Deployment) and FMECA (Failure Mode, Effects & Criticality Analysis). QFD enables transforming the functional/life critical VoC or requirements to CTQs, deriving physical-functional domain interactions and deriving rankings for various test items. FMECA enables criticality assessment for failure modes and defines weighing factors for predominant failure modes. This method works best for projects where we have iterative design process. It offers agile and efficient reliability apportionment that can be deployed in early phases of design, thereby accelerating design for reliability deployment.
Sajjan Phalle, VijaySoma, Nagaraju
This Handbook provides “how to” guidance to industry and government for the reliability Activities and Methods contained in GEIASTD0009 for developing reliable products and systems, successfully demonstrating them during test and evaluation, and sustaining them throughout the system/product life cycle. GEIASTD0009 requires the developers and customer/users working as a team to plan and implement a reliability program that provides systems/products that satisfy the user’s requirements and expectations using a systems engineering approach. The four Objectives of GEIASTD0009 are listed below: Objective 1: Understand customer/user requirements and constraints. The team (developer, customer, and user) includes the Activities necessary to ensure that the user’s requirements and product needs are fully understood and defined, so that a comprehensive design specification and Reliability program plan are generated. Objective 2: Design and redesign for reliability. The developer implements a set of engineering Activities so that the resulting system/product satisfies the customer’s documented requirements and needs. Objective 3: Produce reliable systems/products. The developer performs the Activities that assure the customer that the reliability requirements and product needs have been satisfied. Objective 4: Monitor and assess user reliability. The team establishes a closed-loop feedback Method for continuous monitoring of reliability trends and incorporation of recommended improvements (corrective actions). GEIASTD0009 and this Handbook define a systematic approach to engineering a system/product, incorporating best practices that have evolved considerably in recent years. Figure 1 shows the four Objectives, defined in 1.4.2 of GEIASTD0009, and is a defense industry example of the interaction of the Objectives, supporting Activities and Methods, and strategies for reliable system design in the acquisition cycle. The four Objectives in GEIASTD0009 have Activities associated with them. These Activities are further developed in this Handbook as shown in Figure 2. The four Objectives of the standard are shown on the left and the derived Activities in the Handbook are on the right.
G-41 Reliability
The automotive industry is dramatically changing. Many automotive Original Equipment Manufacturers (OEMs) proposed new prototype models or concept vehicles to promote a green vehicle image. Non-traditional players bring many latest technologies in the Information Technology (IT) industry to the automotive industry. Typical vehicle’s characteristics became wider compared to those of vehicles a decade ago, and they include not only a driving range, mileage per gallon and acceleration rating, but also many features adopted in the IT industry, such as usability, connectivity, vehicle software upgrade capability and backward compatibility. Consumers expect the latest technology features in vehicles as they enjoy in using digital applications in laptops and mobile phones. These features create a huge challenge for a design of a new vehicle, especially for a human-machine-interface (HMI) system. A typical New Product Introduction (NPI) cycle in the automotive industry may range between two and five years, but rapidly changing technologies in the IT industry may evolve into a next generation in just three to six months. The traditional design methodologies in the automotive industry usually require clear boundary conditions before a team can develop a device or system in a vehicle. The definition of boundary conditions is based on empirical data or market survey results. For example, Many OEMs utilize Quality Function Deployment (QFD) to transform customer needs into the design of engineering functions and detailed parameters. However, due to the intersection of the automotive industry and the IT industry, the boundary conditions for a human-machine-interface (HMI) system become unstable, and it is risky to design a HMI system based on the assumption that the boundary conditions will not change during a NPI cycle. With the fast growing autonomous technologies, a modern vehicle may have a totally different HMI system compared to that of traditional cars. With more and more disruptive technologies are introduced in the automotive industry, customers’ voices also became blurring. Sometimes, the majority of customers do not know a future trend and whether they will like these changes. If a development team design a HMI system purely based on the history data or market surveys, the team may lose a foresight. This paper discusses a design method for a modern vehicle’s HMI system. A persona is introduced in the design process and co-creation is utilized to generate design options. A final solution is selected based on psychological and statistical analysis. A design case for the Chinese Automotive market is also elaborated in the paper as an example.
Li, XinyuGe, XinyuWang, Ying
Paddy farming in India requires extensive water use. Due to the rapidly declining groundwater and ever-increasing monsoon uncertainty, there is a significant drive on water conservation for paddy farming through sustainable agriculture practices. The wide depth variability of irrigation water in Indian rice fields, as much as 160 mm, necessitates an extra 100 mm of water in the field to provide complete water coverage. This is primarily due to the inaccurate manual land leveling often practiced in Indian paddy farming. However, accurate laser land levelers have been created by integrating low-cost electronics, hydraulics and global positioning system (GPS) technology. This paper provides an overview of current practices and suitable operating procedures to meet the future demand for land leveling. The presentation compares the laser land leveler with GPS land-leveling solutions, examining technical differences and individual merits and limitations. In addition, a stakeholder analysis evaluates the various technology solutions for agricultural practices. Of the world's available cropland, paddy accounts for more than 11%. It is imperative-for agricultural and environmental sustainability, food and water security and greenhouse gas emissions-that paddy rice agriculture is monitored and mapped in a timely and efficient manner. Meanwhile, water-resource management is a major concern because rice paddy is grown in flooded soils. More than 80% of the fresh water in most cases, and as much as 95% in some cases, is used for irrigation in the Asian study area. This degree of irrigation raises concerns about the maintenance and potential contamination of the water supply. Also, greenhouse-gas methane is a byproduct of seasonally flooded rice paddies, contributing to more than 10% of the total methane flux to the atmosphere. In India, rice is grown over a large area and a broad range of landscapes; a wide variation of climatic conditions exist in such a varied landscape. Thus a variety of unique paddy farming techniques have evolved, based on water source (irrigated, rain-fed, deep-water), crop management (single-crop, multi-crop) and seasonality (wet season, dry season).
Gupta, SaurabhMaity, RobeshKulkarani, Shrirang
Evading traffic congestion by personal flying vehicle is still a far fetched dream. Recent advancements in predicting divergence speeds of slung loads using the Continuous Rotation Method (CRM) of airloads measurement has made is possible to obtain complete aerodynamic load maps of objects. In turn this enables on-the-fly system identification and dynamics predictions to ensure safety and smooth rides with slung loads. A concept is proposed for an air-lift service which can transport people with their personal road vehicles over congested areas. QFD and OEC analyses are used to compare different VTOL options for such a system. A pure conventional helicopter with internal or external carriage, a quadrotor, a lighter-than-air (LTA) platform with a quadrotor, and an LTA with cycloidal rotors are compared. The last two are found to be feasible, with only the LTA-cycloidal meeting all requirements when downwash and noise constraints are imposed. A streamlined carriage concept with aerodynamic control surfaces is suggested. A HUMVEE is used as an example where aerodynamic load mapping has been done, and the data used in predicting dynamics. This shows how to estimate the speed constraints to keep oscillations below specified levels, and verify the safety of the flight envelope.
Shukla, DhwanilHiremath, NandeeshKomerath, Narayanan
The purpose of this Interim Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
An automotive vehicle should be designed to satisfy the wants of customers. The key is how to convert voices of customers into engineering languages. In other words, transfer the wants of customers into the right technical characteristics of a vehicle. A questionnaire of customer wants for a CUV (Crossover Utility Vehicle) is created and processed. Using QFD (Quality Function Deployment) and modified KANO model, the relative important degree is obtained from the original relative important degree of customer wants surveyed. Since some information gained is uncertain and the questionnaire sample is limited, a gray correlation analysis method is introduced, which calculates the competitive important degree of customer wants, then the final important degree of customer wants is gained by integrating the relative important degree and the competitive important degree. In order to solve the correlation degree of the wants of customers and the vehicle technical characteristics, Six senior auto experts are investigated through a special designed questionnaire. According to the survey results, a correlation matrix of customer wants and technical characteristics is built up, thus the technical correlation degree of the wants of customers and the vehicle technical characteristics is calculated. Utilizing the final important degree of customer wants and the technical correlation degree, in other words, combining QFD with modified KANO model, the weight factors of the CUV's technical characteristics are set up finally.
Chen, JiaquanQin, MinJin, LinggeTao, LiuJiang, YongfengWang, WeiChang, Yin-Ping
Many high risks of failure in developing and applying new technologies exist in the recent automotive industry because of big volume of selling cars in a global market. Several recalls cost companies more than $ 100 million per problem. New technologies always have uncertainty in performing intended functions at various given conditions despite the fact that engineers do their best to develop technologies to meet all the requirements. Uncertainty of new technologies put companies into danger of failing in their business. Therefore, many companies tend to take interest in reducing risks from the uncertainty in technologies, but the increasing complexity of modern automotive technologies make it difficult to develop complete technologies. A new engineering methodology called SPEED Engineering was introduced to reduce the risks of new technology applications and to facilitate engineers to conceive innovative ideas dominating the market in the future. Also it is used to help engineers solve engineering problems caused by system conflicts or complex factors. It consists of 3 modules: 1) generating new ideas, 2) finding out problems in technologies which ideas were realized into and 3) solving the problems discovered. Engineering methods such as QFD, FMEA, TRIZ and Robust Engineering which are proven to be excellent in many cases are fully or partially used to conduct each module. SPEED Engineering is not simply a mechanical assembly of these methods but a chemically integrated one. Wastes which engineers suffer from in innovation activities like DFSS, Six Sigma and FMEA can be eliminated and more values can be added through this engineering process. Especially, SPEED FMEA, one of the modules of SPEED Engineering, played an excellent role in preventing failures of 407 new technologies from occurring and gave Hyundai Motor Company 1 billion dollars of financial benefits for 2 years.
Han, MiwooLim, YongpyoAn, Seong-ho
Long periods of sitting occur during our day to day life. It has been estimated that up to 80% of our active non-sleeping time is spent in some sort of sitting position during work, recreation, entertainment, commuting, resting, and exercising. As a result, several health effects like numbness, nerve/circulation occlusions, pressure sore, low back pain, and vein thrombosis have been associated with protracted sitting. Numerous researches have been conducted in the area of seat comfort that depended on conventional methods of testing physical prototype of seat model for comfort. The implementation of the seat comfort results are implemented in the next cycle of the design which may take up to three years. Recent advances in new technology, available after the prototype seat comfort testing, may not be incorporated in the next new seat design. This research work is geared towards developing a technique, tool and metric for seat comfort prediction. The approach stems from using System Engineering by Quality Function Deployment (QFD) to inculcate the understanding of the consumers' wants into designing comfort into the seat design process. The resulting QFD and other factors affecting seat comfort such as seat features, anthropometrics, seat design parameters, and sitting time are used to develop a computer model for predicting seat comfort. The model is designed to predict the level of comfort associated with a seat based on sitting time, seat material properties and features before the production of physical seat prototype.
Ojetola, AkindejiOnyebueke, Landon
The exhaust valve plays a role of reducing the mechanical noise and vibration of vehicle by smooth discharging of the vehicle emissions after combustion process in exhaust system of engine. The torsion spring is one of the most core components in exhaust valve, which generates variable torque for control of opening and closing angle of exhaust valve. Its performance represents all over the performance of exhaust system of vehicle. As it were, the failure of torsion spring means the failure of all exhaust system. So, as well as performance, the reliability of the torsion spring is very important. To secure the reliability is same to secure the security and comfort of passengers including driver. This paper proposed two methods for improvement of torque and reliability characteristics of torsion spring. One is improvement of heat treatment condition for getting of more constant torque characteristic of torsion spring. The optimal heating cycle for heat treatment is newly introduced, which is time and temperature concept based on related references and author's empirical knowledge. The propriety of this method is verified through comparison of torque characteristics between before and after heat treatment using the new condition. Another is inducement of design equations for theoretical design and decision of the design parameters. The design equations composed by combination of the manufacturer's opinion, references, and empirical knowledge. The correctness of the design equations are shown by similarity of the torque values between theoretical design and experimental results of prototypes. In addition, we also developed some kinds of failure analysis documents as like FMMA(Failure Modes and Mechanisms Analysis), FMECA(Failure Modes Effects and Criticality Analysis), FTA(Fault Tree Analysis), and 2-Stage QFD(Quality Function Deployment) for reliability assessment of torsion spring. These offer important failure information like major failure cause and effect, life time, test items, and accelerated life factor of torsion spring.
Sung, Baek Ju
This document addresses robustness of electrical/electronic modules for use in automotive applications. Where practical, methods of extrinsic reliability detection and prevention will also be addressed. This document primarily deals with electrical/electronic modules (EEMs), but can easily be adapted for use on mechatronics, sensors, actuators and switches. EEM qualification is the main scope of this document. Other procedures addressing random failures are specifically addressed in the CPI (Component Process Interaction) section 10. This document is to be used within the context of the Zero Defect concept for component manufacturing and product use. It is recommended that the robustness of semiconductor devices and other components used in the EEM be assured using SAE J1879 OCT2007, Handbook for Robustness Validation of Semiconductor Devices in Automotive Applications. The emphasis of this document is on hardware and manufacturing failure mechanisms, however, other contemporary issues as shown in Figure 1 need to be addressed for a thorough Robustness Validation. A Pareto of contemporary issues is shown in Figure 1. Although this document addresses many of the issues shown, however some are outside the scope of this document and will need to be addressed for a thorough RV process application. Examples of issues outside the scope of this document are system interactions, interfaces, functionality, HMI (Human-Machine Interface) and software. At the time of publication of this handbook, a system level Robustness Validation handbook, which addresses these issues, had been initiated.
Automotive Electronic Systems Reliability Standards
This document discusses a recommended new approach to integrate probabilistic methodologies with design practices, procedures, and software codes currently being used. In addition to complementing design methods currently in use, this new procedure will permit the designer to quantify the amount of conservatism that exists for a particular design due to the large amount of additional information which is provided to the designer. This additional information will allow the designer to make better decisions when faced with tradeoffs between cost, reliability, performance, and weight. Although the methodologies described herein can be used heavily in the design process, their applicability is much more encompassing. They can be used from product concept to customer delivery.
G-11 Probabilistic Methods and Uncertainty Quantification
The importance of reliability in design engineering has significantly grown since the early 1960’s. Competition has been a primary driver in this growth. The three realities of competition today are: world class quality and reliability, cost-effectiveness, and fast time-to-market. Formerly, companies could effectively compete if they could achieve at least two of these features in their products and product development processes, often at the expense of the third. However, customers today, whether military, aerospace, or commercial, have been sensitized to a higher level of expectation and demand products that are highly reliable, yet affordable. Product development practices are shifting in response to this higher level of expectation. Today, there is seldom time, or necessary resources to extensively test, analyze, and fix to achieve high quality and reliability. It is also true that the rapid growth in technology prevents the accumulation of historical data on the field performance of their products. Unfortunately, some reliability methods have depended upon the availability of historical data, other experiential information, or learning through extensive and time consuming tests. The new realities require innovation and creativity in the selection and use of reliability methods, and teamwork and collaboration in the management of product development programs. There must be a shift from seeking to eliminate complaints in products, to eliciting praise for them. To enable this transition, reliability efforts must be directed toward anticipating problems and designing-in features that assure the achievement of quality and reliability, concurrent with the development process, instead of trying to assess quality and reliability downstream. The gains in time-to-market and cost savings from such an approach can be significant. More recent reliability programs tend not to prescribe reliability tasks or methods to be performed by suppliers. Rather, suppliers are considered equal partners in the effort to produce a reliable product and work with the companies in deciding which reliability methods provide most value in achieving objectives. Nevertheless, developing reliable products and achieving reliability goals often requires different approaches for various product sectors. For example, in the defense/aerospace sector, the number of customers is relatively small. The product development cycle may span several years, while the product life cycle may last from mere minutes to as long as decades. Furthermore, it is not unusual for several design iterations of technologically different hardware and software to be developed before the final version is incorporated into the production product. Production volumes may range from rates of less than ten to hundreds per year. Also, the reliability discipline in this sector is generally a separate activity from the design discipline. The commercial sector, in contrast to the defense/aerospace sector, usually has a higher number of different customers. Development cycles could range from months to a few years while life cycles are often measured in years. Production volumes may run up to thousands per day. The reliability discipline is treated usually as an integral part of the up-front design process rather than a separate activity. Thus, developing a reliability implementation guide to meet the needs of all industry sectors is a formidable challenge. It recognized that this Guide will not strictly apply to all situations or industries. The suggestions made in this Guide must be interpreted in the context of the industry, its accepted practices, and unique company policies. The following statement will be repeated several times in this document to emphasize its importance: “The selection of methods is a highly individualized process. This point cannot be overemphasized and this document does not attempt to prescribe any given method or set of methods. There is no right answer that will apply across the board to every organization or every product development. Suppliers and customers need to determine which methods are most applicable to their specific product developments.”
G-41 Reliability
The Common System Requirements Analysis (CSRA) method in the avionics system design domain was presented in this paper. The CSRA method was improved from the Quality Function Deployment (QFD) method. The basic principle and the analysis steps of the CSRA were depicted. A practical case of the common avionics system requirements analysis and three proposals assessment was executed by adopting the CSRA method and its results. The case application showed the feasible and capability of the CSRA method on the design procedures of common avionics system of a multisystem, such as the Series Rotorcraft Unmanned Aerial System (SRUAS), which have several independent systems for different types of missions. The CSRA can enable the higher quality, lower cost, and shorter development period of the common avionics system.
Zhu, MingZhang, LeiSong, JingjingWu, Zhe
This document provides information to help the reader view maintainability in the context of an overall systems engineering effort. The guide defines maintainability, describes its relationship to other disciplines, addresses the basic elements common to sound maintainability programs, and describes the tasks and activities associated with those elements.
G-11M, Maintainability, Supportability and Logistics
An existing pass by noise data acquisition system was upgraded to provide the sophisticated data analysis techniques and test site efficiency required to comply with the current and future drive by noise regulations. Use of six sigma tool such as voice of the customer helped in defining the customer requirements which were then translated into the desired engineering characteristics using QFD. Pugh concept matrix narrowed down the best option suitable for the test site modifications taking into account the critical constraints such as test complexity, system cost & transparency to the existing drive by noise setup. Features of the new system include data telemetry, frequency analysis, portability and efficient data management through the use of advanced data acquisition system. Wireless mode of the data transmission helped significantly avoid most of the test site modifications, which in turn helped to reduce the overall system implementation cost. The benefits of the improvements included providing suitable platform to share test results with internal and external customers (OEMs) with improved data quality. The system generates accurate, dependable data in a final test report at the conclusion of each test minimizing manual data entry and driver subjectivity in validating the test runs.
Purekar, Dhanesh
Recent development in automobile industries has seen increased customer attention for good door slamming noise. One of the constituent which plays major role in building brand image of vehicle in terms of NVH performance is door slam noise quality. Hence it is very desirable to understand how different door elements radiate sound during a door-closing event and how to optimize a door structure to achieve specific sound target in order to ensure the door closing noise quality, NVH engineers needed to look at contributions from different door subsystems. The use of statistical tools like Six Sigma can further help them to ensure the consistency in results. This paper explains the systematic approach used to characterize different element of door which contributes to the overall door slam noise quality through QFD (Quality Function Deployment) and contribution analysis. The different mechanisms contributing to door slam noise were studied. NVH characteristics (Acoustic transfer Function and Point Mobility) of the door structure and mounting locations were captured for correlating with the time - frequency spectrum of door slam event. Wavelet analysis was performed on door impact event to determine the critical frequency band contribute to noise. DOE (Design of Experiments) was constructed based on the analysis of results. Prototype modifications were conducted, the results of which are discussed in the paper together with their relative importance to work improvement in door closing noise. Finally the design intent solutions were developed together with component supplier and are validated on vehicle.
Bhangale, RajeshMansinh, Kumbhar S.
The paper presents a development strategy for a Low Cost Vehicle (LCV) concept set at a target MSRP of $8000 (USD) for the U.S. market. Tata Nano, currently the world's cheapest car in production, is developed on similar principles of the Ford's Model T concept. This paper adopts a similar methodology behind the development of the Tata Nano and is considered as the starting point for the LCV development. It gives an overview of the unique product development process of the ‘Tata Nano’ and shows the possibility of applying similar methodologies, based on systems engineering principles, for future low cost vehicles which will be suitable for the American market. The major automotive systems were assigned specific cost targets based on the set target cost of $8000 (USD) for the LCV. The specifications of the systems were derived based on customer needs and the U.S. Federal Motor Vehicle Safety Standards (FMVSS) using analytic tool Quality Function Deployment (QFD) and by comparing and benchmarking current vehicles sold in US for its specifications. System level modifications necessary to comply with the FMVSS are considered. Adhering to the Systems Engineering principles, sales volume, target customers, manufacturing & assembly factors are discussed to realize the importance of integrating all aspects of vehicle product development, to achieve the final target.
Tajmahal, HussainRanadive, Shantanu
In a very competitive environment, product development in automobile industry needs to be fast paced with best in quality to stay ahead in the race. Therefore a clear understanding of customer requirements is essential in successful design and development of systems. Failure in any system development step can result in costly design and tooling changes, schedule delays and ultimately, customer dissatisfaction. A team was formed to design and develop an automotive system by applying Design for Six Sigma Green Belt methods and tools. The hypothesis of this study was that a substantial opportunity exists to increase project efficiency while providing what customer wants, by following a standardized statistical work practice for managing requirements throughout the life of product development using the methodology of Design for Six Sigma DMADV (Define, Measure, Analyze, Design and Verify). In this paper an automotive HVAC system is designed following DFSS methodology. The application process of DFSS tools like Kano analysis for Voice of Customer, Monte Carlo Simulation for project duration calculation, Measurement System Analysis, Quality Function Deployment (QFD), Triz- contradict problem solving technique, Pugh matrix, Design of Experiment (DOE) strategies and process capability for HVAC system development is discussed. The paper will also present how the DFSS process can improve project performance, cost and time while delivering quality products to the customer.
Patidar, Ashok
Motorized closures support the comfort in vehicles to an increasing degree. In the past the use of indirect sensors was an effective low-cost solution for anti pinch [1,2]. The demand for a reduction of the forces affecting the user and for minimized closing times leads to direct sensor solutions. A new aspect is the protection of moving vehicle parts, which we call collision avoidance. This paper deals with system aspects securing the movement area of motorized closures. An analysis is made for sliding doors, trunk lids and tailgates, pointing out the danger zones and the use cases. The result of a QFD (Qualitiy Function Deployment) with respect to the demands of the customer is shown. This leads to a rough description of the requirements for the technical solutions. A technology benchmark is conducted separately for anti-pinch and for collision avoidance. The two applications have distinct requirements; therefore different technological solutions are identified. As an example, the tailgate is examined in detail and a solution for securing the danger zones is presented. A Lab car is equipped and tested. For anti-pinch, a capacitive sensor system is selected and designed. Collision avoidance is realized by adopting a series automotive ultra-sonic sensor. Environmental influences are examined and described. Special integration problems and their solutions for both sensor systems are discussed. The topology of the electronic components is described and an outlook on the future is given.
Nitsche, BrigitteHerrmann, Rolf
Quality Function Deployment (QFD) and Pugh Matrix on Innovative Concept Selection: an Application in Automotive Sector2008-36-001710/7/2008
This paper aims to present an application of some quality tools focused on best concept identification process to meet defined customer requirements in activities of process development in an industry of automotive sector. First of all it was done a literature review in order to clear establish the concepts of the following tools: “voice of the customer”, “affinity diagram”, “pair wise comparison”, “quality function deployment (QFD)” and “Pugh matrix”. After it is presented the application of these tools in activities of technology research of advanced engineering department. The first task was to identify all customers related to the process in study. After this, some interviews were scheduled with them and the entire “voice of customer” was collected. With all this information it was used “affinity diagram” to summarize the inputs and used “pair wise comparison” to prioritize customer needs. To translate voice of customer into measurable parameters it was used QFD. The output of this process was a prioritized list of “critical to quality” parameters (CTQ). Finally, to select the best concept it was used “Pugh matrix” evaluating all potential concepts according to CTQ list. According to the results obtained it was possible to conclude that the use of a methodology has changed the way we would follow. This work was related to the technology identification to a process to join metal pieces. Initial idea was to use a certain technology and all team trusted on that. The methodology showed that it does not work and presented a very simpler and cheaper technology that met all customer requirements.
Fernandes, Marcelo MachadoRosati, Antonio CesarNeto, Didimo GarciaGoto, Frank KenjiMaciel, HelioMologni, Juliano Fujioka
This standard requires the developers and customer/user’s working as a team to plan and implement a reliability program that provides systems/products that satisfy the user’s requirements and expectations. The user’s requirements and needs are expressed in the form of the following four reliability objectives: The developer shall solicit, investigate, analyze, understand and agree to the user’s requirements and product needs. The developer, working with the customer and user, shall include the activities necessary to ensure that the user’s requirements and product needs are fully understood and defined, so that a comprehensive design specification and Reliability Program Plan can be generated. The developer shall use well-defined reliability- and systems-engineering processes to develop, design, and verify that the system/product meets the user’s documented reliability requirements and needs. The developer shall implement a set of engineering activities (included in this standard as normative activities and informative activities, refer to Section 3) so that the resulting system/product satisfies the customer’s documented requirements and needs. The multifunctional team shall verify during production that the developer has met the user’s reliability requirements and needs prior to fielding. The developer shall include activities that assure the customer that the reliability requirements and product needs have been satisfied. The multifunctional team shall monitor and assess the reliability of the system/product in the field. The team is responsible for identifying the data elements to assess the reliability of the system/product in the field and to ensure the data collected are accurate and complete. The team will establish a closed-loop feedback method to flow recommended improvements (corrective actions) for monitoring reliability growth.
G-41 Reliability
The Value of Joint Customer and Supplier Quality Function Deployment (QFD) and Design for Six Sigma (DFSS) Toolset Applications2008-01-03604/14/2008
The purpose of this paper is to show the power of joint ownership between suppliers and customers to create a superior product for the end user. This effort translates into competitive advantages for all parties involved in the learning. The advantages of the customer and supplier working together through the Quality Function Deployment (QFD) and the “Design for Six Sigma” DFSS methodology will be discussed. DFSS is a design approach and tool set which is typically applied to new concepts or future creations. This paper will highlight how the same tool set is utilized to make an existing no clean solder paste formulation robust to changes in raw materials. • DFSS QFD Toolsets which were used included: House of Qualities Balanced Scorecard Desirability Curve Measurement System Evaluation (MSE) Regression Through the application of DFSS the team was able to break the 5σ wall for solder paste performance in automotive electronics assembly processes. Other unique topics discussed are Mixture DOE (Design of Experiments) strategies, their application, and their comparison to classical DOE strategies in a complex material formulation. The mixture design incorporated over 20 outputs (Y's) over 7 factors (X's). This enabled the team to maximize the solder paste formulation for desirability, and achieve minimum risk and variability. The paper will also address the issues involved with large scale projects and how this joint effort broke the project down into manageable pieces through the creation of sub-projects. This approach enabled the team to remove internal and external barriers through effective project communication.
Sanftleben, HankLewis, LloydStark, KrisYoung, MarySkrzat, Mike
Application of QFD: the Formula SAE design considering the Supply Chain2006-01-274711/21/2006
Before the changes occurred in the production spectrum, communication needs to become more efficient. Hard competition in global market leads to decrease of the cycle time of product design. To improve research inside the industry, the use of management tools to robust design must be complemented with efficient communication's systems between Supply Chain and Product Design Process. This necessity can be proved studying the application of the management tools (QFD - Quality Function Deployment) to Product Development in a Formula SAE team. Its results, in a qualitative view, indicate the economic viability and the cost deployment to minimize the design stage and points up these multifunctional research teams structure and this professional graduate as a way to satisfy the communication failures. Diante das mudanças ocorridas no cenário produtivo, a comunicação necessita se tornar muito eficiente. Para aprimorar o trabalho de pesquisa, o uso de ferramentas de gestão para projeto robusto precisa ser complementado com sistemas de comunicação eficientes entre a cadeia de suprimentos e o processo de desenvolvimento de produto. Pode-se comprovar com um estudo de caso da aplicação de uma ferramenta em uma equipe de Fórmula SAE. Os resultados indicam o grau da necessidade da viabilidade econômica como forma de encurtar tempo do ciclo, bem como questionam a estrutura das equipes de pesquisa multifuncionais e a formação dos profissionais envolvidos.
da Costa Teixeira, Maria ClaraNeto, Álvaro Costa
The general requirements of an SPC system shall encompass, but are not limited to, the following elements: a Overall quality system b Management commitment c SPC system documentation d Critical process nodes e Gage characterization and capability f Process characterization and capability g Control system documentation h On-line/off-line control i Training j Supplier SPC systems k Calibration l Preventive maintenance m Self audit
Systems Management Council
Quality Function Deployment for the Shoulder Section of the Space Suit2005-01-30177/11/2005
Spacesuit shoulder mobility is critical in performing EVA tasks. In addition, risk of failure must be minimized and injuries during operations and training eliminated. The pressure suit design elements that control shoulder mobility interact strongly and in complex ways with many aspects of the pressure suit and system design and are constrained by anthropometric factors. To properly develop the problem statement for the shoulder section in a new suit design that is appropriate for a return to the Moon and eventual exploration of Mars, a Quality Function Deployment (QFD) is under development. QFD is a powerful and widely used method to define your customers, determine their needs, benchmark the competition, and define engineering parameters and targets, that when met, will lead to a successful product. Since many of the requirements for the next generation suit are unknown, the QFD will continually be updated. The engineering parameters, which are tests or measures that must be specified such as range of motion, are critical to develop a successful design. Due to the difficulty and expense of performing these tests, it is challenging to develop an appropriate set of measures. These will be added to the QFD as NASA and its contractors develop them. This paper describes the application of the quality function deployment process to a spacesuit shoulder mobility joint.
Adrezin, RonaldZaccaro, LaurenHodgson, EdwardTrevino, Robert
Development of Specifications for the UM-D's Low Mass Vehicle for China, India and the United States2005-01-10274/11/2005
This paper presents results of a research project conducted to develop a methodology and to refine the specifications of a small, low mass, low cost vehicle being developed at the University of Michigan-Dearborn. The challenge was to assure that the design would meet the needs and expectations of customers in three different countries, namely, China, India and the United States. U.S, Chinese and Indian students studying on the university campus represented customers from their respective countries for our surveys and provided us with the necessary data on: 1) Importance of various vehicle level attributes to the entry level small car customer, 2) Preferences to various features, and 3) Direction magnitude estimation on parameters to size the vehicle for each of the three markets. Our specification process involved: a) Development of a generic vehicle level Quality Function Deployment (QFD) analysis to relate customer needs to engineering attributes, b) Conducting a literature survey of various existing requirements and regulations on vehicles, c) Using importance ratings on various customer needs and vehicle attributes obtained from our subjects from the three countries, d) Sizing the vehicle for respective markets from the direction magnitude scaling, and e) Selecting base and optional feature content for the three markets from the customer ratings. The results of the analyses showed that: 1) Low vehicle cost emerged as the single most important vehicle level attribute from the QFD chart. 2) Fuel efficiency, durability and serviceability, from the customer importance rating survey, were the most important vehicle attributes, 3) One vehicle configuration would not be suitable for all the three markets without some modifications to satisfy the significant differences observed among the three countries. For example, a HVAC system was absolutely necessary to 94% of U.S. customers, but Indian customers had no need for it. Fog lamps were absolutely necessary to about 76% of Chinese customers but only less than 16% of U.S. customers and only about 6% of Indian Customers wanted them. 4) Indian customers wanted smaller wheelbase as compared to the U.S. and Chinese customers.
Natu, MangeshBhise, VivekShulze, Roger
This document provides information to help the reader view maintainability in the context of an overall systems engineering effort. The guide defines maintainability, describes its relationship to other disciplines, addresses the basic elements common to sound maintainability programs, and describes the tasks and activities associated with those elements.
G-11M, Maintainability, Supportability and Logistics
The purpose of this Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
The pursuit of a dominating diesel engineAUTOFEB01_092/1/2001
Engineers at Cummins and Detroit Diesel believe the diesel engine will assume a larger share of future light-truck sales. Two manufacturers with solid reputations in the heavy-duty engine field are taking aim at the light-duty market. Light trucks, which include pickups, SUVs, and vans, comprise over 50% of family vehicles in the U.S. Automakers have repeatedly increased light-truck vehicle size in response to customer demand. These marketing characteristics coupled with relatively low fuel prices within the U.S. have drastically changed the product mix away from smaller, more fuel-efficient cars toward larger, more profitable light trucks. This trend has also resulted in decreasing fleet fuel economy average, making it difficult for automakers to reach CAFE targets. Detroit Diesel Corp. (DDC) developed an engine specifically for the North American light-truck market, with the first engine firing just 228 days after pencil touched a clean sheet of paper. The process began with a quality function deployment (QFD) analysis, which prioritized the development criteria. QFD captures primary customer wants, and through an unbiased process, evaluates tradeoffs and dependencies. In the first QFD phase, these parameters are reduced to technical system expectations, which form the basis for the second QFD phase and, ultimately, the engine-design process. The development process integrated a colocated, fully cross-functional team among suppliers and DDC. The first demonstration vehicle was driven 12 weeks after the first engine fired.
Competitive positioning, benchmarking and target setting2000-05-02246/12/2000
Automotive product definition involves the use of various tools and techniques to position a new vehicle in a competitive marketplace. The desire of VMs to produce successful products, with high levels of customer appeal, in very short timescales has led to the adoption of more rigorous product definition processes including empathic design, competitor benchmarking and Quality Function Deployment (QFD). These, in combination with a much greater reliance on a predictive engineering methodology, are being utilized to provide a "right first time" approach in the achievement of this goal. The Kano model introduced in the early 1980s emphasizes that, to truly satisfy and delight customers, a product must possess "excitement quality." Empathic design is employed by many VMs to identify product features or attributes that will deliver such qualities. Many VMS use competitor benchmarking methods to understand their competitors'' products, in particular, the mechanisms and technology employed to achieve desirable attributes. QFD is widely used as an effective means of ensuring the customer requirements are considered through the engineering process and reflected in the end product. This paper discusses the application of these tools and techniques in the product definition process and how they are used to position new products in an increasingly competitive market place.
Spall, TerryAhn, Yun-Sang
The procedure outlined in this document is applicable to any manufacturing or service process. It may be used on part of a process or and entire process or a series of sequential processes.
Systems Management Council
Long-Time Observation: New Aspects for the Development and Analysis of Mechatronic Systems - The Automated Clutch System of the Mercedes A-Class as an Example2000-01-08393/6/2000
An effective development strategy is needed to implement short development times for mechatronic systems, which themselves are becoming increasingly more complex. Besides the ever-increasing use of advanced computer-based development tools, special attention must be paid to the validation of the functional behavior of the prototype during all phases of the development process. Using the example of systems for powertrain automation, this paper depicts the resulting advantages arising from the long-time observation of time-based values of open- and closed-loop controlled systems. The method of long-time observation introduced here is based on the acquisition and analysis of information in all phases of the development process. Where numerous vehicles are already in the hands of selected customers during fleet tests, these late phases in particular are covered thoroughly. It should be noted that newly developed systems are normally unobserved or only subjectively evaluated by the driver. New aspects arise regarding the evaluation of the control system behaviour, its quality and its reliability, as the system is in use in real-word operating conditions over a broad range of different and partially extreme operating conditions, enabling the system designer to reproduce and observe all desired and undesired effects. In particular, hard-to-reproduce effects, such as the detection of sporadic faults in specific operating situations or unpredicted interactions with particular drivers, can be proven with long-time data acquisition and observation strategies. New aspects also arise in the fact that the method introduced here comprises in particular the synchronous/parallel acquisition and analysis of internal and external data of the electronic control system (ECU). The ability to compare ECU-internal and external data is an essential contribution for control strategy optimization and validation, not only for the confirmation of diagnosis functions, but also for the check-up and evaluation of calibration values. An essential prerequisite is an unobtrusive data acquisition system, which can utilize data from vehicle data-buses and other digital interfaces, such as for diagnosis and calibration purposes, as well as from analogue sensors. As the data produced here contains a large amount of real-world elements produced by the customers themselves, it can also be used for investigations under statistical aspects: The elaboration of suited data logistics leads finally to a database, which can be used for a broad range of statistically ensured investigations and analysis tasks. Examples given here include user and load profiles, the driving behavior of specific user groups and the estimation of component characteristics. The chosen method contributes directly to the inclusion of the customer as the driver, demanded, for example, in Quality Function Deployment during customer orientated product development.
Pfund, ThomasLudes, Reinhard
Aluminum alloy heat exchangers use chromium (VI) compound for their surface treatment to prevent white rust. The use of chromium (VI) compound is restricted and will be banned worldwide in view of environmental concerns. Therefore, we need a timely change to the non-chromate type treatment. Considering this trend, we have developed and released non-chromate type heat exchangers. In addition to high corrosion resistance, these heat exchangers feature a good hydrophilic ability, antibacterial activity, and smell preventing property. With simultaneous development activities at the development and design divisions, as well as making good use of the quality function deployment (QFD) method into the total process from design work to production we have completed the project in a short time.
Yamazaki, EtsukoUehara, ToshiyukiYoshida, Chizuko
Items per page:
1 – 50 of 82