Pnashev Flashcards
Methods of Quality Engineering
• QFD – customer requirementsvs. quality characteristics of products or services
• FMEA – risk analysis with regard to the fulfilment of
requirements
• DOE (Design of Experiment) – optimisation of products und processes by systematic experimentation
• SPC (Statistical Process Control) – regulation and improvement of processes by statistical models and
methods
Quality Function Deployment
What does that mean?
• Q (= Quality): to plan the quality which is
required from the customer
• F (=Function): to ensure the required quality
across the enterprise
• D (=Deployment): effectively developing and
making practical use of one’s customer oriented strategy
• QFD is a planning method to translate customer’s requirements into requirements for developers.
• QFD is used during development projects. It tents to cover all customer
requirements and to translate them into measurable quality characteristics.
• QFD was developed in Japan in 1966 and it was used for the first time in 1972
by Mitsubishi
Quality Function Deployment
The Approach
- Determining relevant customer groups
- Registering customer requirements (QFD-CR)
- Deducing quality characteristics (QFD-QC)
- Specification of target figures of the QFD-QC
- Checking interactions (e.g. office hours with number of employees)
- Comparison with the products and services of competitors
QFD – the four phases by ASI
American Supplier Institute
- Product planning
- Component Planning
- Proces planning
- Production planning
Quality Function Deployment
Pros and Cons
Pros
• systematic integration of customer requirements in the development
• competitiveness of concepts can be detected early
• it improves the internal information and communication flow
• number of subsequent changes can be reduced
• shorter development times for new products or services
Cons
• relatively high effort in terms of costs, time and man capacity
• tends to become highly complex (but by the use of IT, it can be controlled)
• risk of translation errors – often customer and developer do not share the
same language (internationalisation)
Failure Mode and Effect Analysis
FMEA
structured tool for identifying, analysing, handling and
avoiding of risks.
There can be risks in products, services, in their development, production or allocation. • The basic idea of the FMEA is the prevention of errors in an early Product Life Cycle (PLC) phase
FMEA
Essentials
- Content: risk analysis of products, processes, systems, etc.
- Starting point: a product, a process, a system but also a function
- Error definition: failure (negative effect, no function or malfunction, etc.)
FMEA
Types
Product-FMEA (also called Design- or Development-FMEA)
• risk management for all products or for individual
modules or components of a product.
Process-FMEA
• risk management for production & assembly processes,
logistics or business processes in general.
• 4Ms ( ……………………………………. ) => starting point for possible failure!
System-FMEA
• risk management for complex systems,
• interaction of the individual system elements with each other,
• analysis of important functional relationships of the system elements.
• Application: Systems Engineering, Product and Process Development.
(Mensch, Maschine, Material & Mittel)
Man, M
The method of reliability analysis
Bottom-Up ( Inductive) vs. Top-Down (Deductive)
FMEA
Risk Prioritisation
Function of risk assessment = quantifying the severity of a failure, the
probability of its occurrence and its detection.
• The evaluation of the failure => Risk Priority Number (RPN) = (O) x (I) x (D)
• The evaluation of the individual items is made by a scale of 1 (»no risk«) und
10 (»highest risk«) => RPN Є (1, …, 1000).
• Exceed the Risk Priority Number (RPN) a predetermined value (for example
RPN > 125), improvement activities should be taken.
(O) = probability of occurrence (failure cause and frequency)
(I) = impact of the failure (severity)
(D) = probability of detection (… by the customer, after delivery)
FMEA
Pros and Cons
Pros
• early detection of possible failures of a new product or service
• estimating and quantifying of risk resulting from possible failures
• implementation and evaluation of all possible activities for improvement
Cons
• relatively high costs and efforts
• the risk estimation is subjective
• the impact of individual failures can be detected, but not their interaction