1. Chap 10 Managing Engineering Design

2. Advanced Organizer

3. Chapter Objectives
Describe the phases or stages in systems engineering and the new product development process
Recognize product liability and safety issues
Recognize the significance of reliability and other design factors

4. Nature of Engineering Design
Eng. Design Process
Information:
Statement of the problem
Design standards
Design methods
Information:
Drawings
Specifications
Financial estimates
Written reports
Oral presentations

5. SYSTEMS ENGINEERING/ NEW PRODUCT DEVELOPMENT
The design of a complex engineered system, from the realization of a need through production to engineering support in use is known as systems engineering (especially with military or space systems) or as new product development (with commercial systems).

6. New Product Development - Stages
Conceptual
Technical Feasibility or Concept Definition
Development
Commercial Validation
Production
Product Support
Disposal Stage

7. Systems Engineering Process (In each phase of development)
Requirements Analysis: Analyze customer needs, objectives, and constraints to determine the functional requirements.
Functional Analysis/Allocation Identify lower level functions needed to meet these functional requirements, and translate them into design requirements suitable as design criteria.
Synthesis. Define the system concept, configuration item alternatives and select the preferred set of product or process solutions to the level of detail required in the phase being conducted.

8. Systems Engineering Process (In each phase of development)
System Analysis and Control. Provide the progress measurement, assessment, and decision mechanisms required to evaluate design capabilities and document the design and decision data.
Trade-off (trade) studies
Risk management
Configuration management
Interface management
Systems engineering master schedule (SEMS)
Technical performance measurement (TPM)
Technical (design) reviews

9. Quality Function Deployment (QFD)
Quality function deployment is a team-based management tool in which the customer expectations are used to drive the product development process.
Conflicting characteristics or requirements are identified early in the QFD process and can be resolved before production.

10. Quality Function Deployment (QFD)
Key benefits:
product improvement,
increased customer satisfaction,
reduction in the total product development cycle, &
increased market share.

11. Quality Function Deployment (QFD)
Identify User Needs & Wants
Gather raw data
Interviews
Focus Groups
Observation
Interpret raw data
Affinity Diagram
Needs Statements
Organize needs & establish importance
Surveys
Conjoint Analysis

12. Quality Function Deployment (QFD)
Identify User Needs & Wants
Gather raw data (Interview Segmentation)
Non-Traditional Segmentation
Traditional Demographic Segmentation

13. Quality Function Deployment (QFD)
Identify User Needs & Wants
Gather raw data (How many interviews are needed? )

14. Quality Function Deployment (QFD)
Identify User Needs & Wants
Gather raw data (Focus Groups)
From: Griffin, Abbie and John R. Hauser. “The Voice of the Customer”, Marketing Science. vol. 12, no. 1, Winter 1993.
One-on-One Interviews (1 hour)
Focus Groups (2 hours) 1 2 3 4 5 6 7 8 9 10 20 40 60 80
100
Percent of Needs Identified
Number of Respondents or Groups

15. Quality Function Deployment (QFD)
Identify User Needs & Wants
Interpret raw data
Affinity Diagram
Organizes subjective information
Example: Group the following CR’s
“ease of handling”
“portability”
“number readability”
“load handling”
“ease of use”

16. Quality Function Deployment (QFD)
Identify User Needs & Wants
Interpret raw data (Needs Statements)
What, not How
Be specific
Positive, not negative
Attributes of the product
Avoid “must” or “should”.

17. House of Quality

18. Technical Descriptors
Interrelationship
between
Technical Descriptors
(Voice of the Organization)
Relationship between
Requirements and Descriptors
Prioritized Technical Descriptors
Prioritized Customer Requirements
Customer Requirements
(Voice of the Customer)
Prioritized Customer Reqmts
Customer Reqmts

19. 4 Phases of QFD

20. Classical Model of QFD Matrix What How House of Quality
Voice of Customer
Tech. Performance Measures
Subsystem Design Matrix
Piece/Part Characteristics
Piece/Part Design Matrix
Process Parameters
Process Design Matrix
Production Operations

21. Portable Slide Projector Example
Customer Needs
Good image
Easy to transport
Keeps present. flowing
Image visible in bad conditions
Minimizes unplanned interruptions
Design makes the product attractive
Device sets up quickly
Works well for short present.
Engineering Metrics
Brightness
Weight
Dimensions (girth + width)
Time/Tasks required to start present.
Distortion
Distance from presenter
Time to insert/pull-out slide
Attractive product
Portable Slide Projector
Example

22. Phase I -
Portable Slide Projector

23. Phase II -
Portable Slide Projector

24. Phases in Systems Engineering / New Product Development (DoD)
Pre-milestone zero studies
Concept exploration & definition
Demonstration and validation
Engineering and manufacturing development
Production and deployment
Operations and support

25. Phases in Systems Engineering / New Product Development (NASA)
Conceptual design studies
Concept definition
Design and development
Fabrication, integration, test, and certification
Pre-operations
Operations and disposal

26. Phases in Systems Engineering / New Product Development (NSPE/NIST )
Conceptual
Technical feasibility
Development
Commercial validation and production preparation
Full-scale production
Product support

27. Tasks Within Each Phases of Systems Eng. /New Product Development
Approval to expend the resources / agreement on the work to be accomplished.
Accomplishment of the work
Compile the results: designs and specifications, analyses and reports, and a proposed plan for conducting the following phase if one is recommended.
To cancel the development,
To go back (recycle) and do more work in the present phase; or
To proceed with the next phase.

28. Conceptual stage
Statement of the design problem, clearly defining what the desired intended accomplishment of the desired product
Key functions
Performance characteristics
Constraints
Criteria of judging the design quality

29. Conceptual stage Musts: requirements that must be met
Must nots: constraints defining what the system must not be or do
Wants: features that would significantly enhance the value of the solution but are not mandatory (to which an additional, even less compelling category of "nice to have" is often added)
Don't wants: characteristics that reduce the value of the solution

30. Conceptual stage (Kano’s Model)
Actual Performance
Customer Satisfaction
Satisfiers
Dissatisfiers
Delighters

31. Conceptual stage (Kano’s Model)
Expected Quality
Dissatisfiers
Smooth Surface
Scratches, blemishes
All parts work
Broken parts
Clear instruction
Missing instruction
Normal function
Function not provided
Product is safe to use
Product is unsafe
Product conforms to std.
Product is non-conformant

32. Conceptual stage (Kano’s Model)
Satisfiers:
Desired Quality
Performance Measure
Direction
Capacity
Cubic feet of storage
LargerTB
Price
Dollars
SmallerTB
Reliability
MTBF
Speed
Transactions /second

33. Conceptual stage (Kano’s Model)
Examples of Delighters
Sony Walkman
3M Post-it
Cup Holder
One-touch recording
Redial button on telephone
Graphic User Interface (GUI)

34. Results from Conceptual stage
A set of functional requirements
Identification of the potential barriers to development, manufacturing, and marketing the proposed product.
Test-of-principle model to reduce technical uncertainties
Order-of-magnitude economic analyses and
Preliminary market surveys to reduce financial uncertainty.

35. Importance of Conceptual stage
1% of the cost of the product
70 % of the life-cycle cost

36. Technical feasibility stage
The objectives of this stage are
To confirm the target performance of the new product through experimentation and/or accepted engineering analysis and
To ascertain that there are no technical or economic barriers to implementation

37. Technical feasibility stage
Typical steps:
Subsystem identification
Trade-off studies
System integration
Interface definition
Preliminary breadboard-level testing
Subsystem and system design requirements (reliability, safety, maintainability, and environmental impact).
Development of preliminary test plans, production methods, maintenance and logistic concepts, and marketing plans.
Preliminary estimation of the life-cycle cost of the system.
Preparation of a proposal for the development stage

38. Importance of Technical feasibility stage
7% of the cost of the product
85 % of the life-cycle cost

39. Development stage (Build-test-fix-retest sequences)
The objective of this stage is
To make the needed improvements in materials, designs and processes and
To confirm that the product will perform as specified by constructing and testing engineering prototypes or pilot processes.

40. Commercial validation and Production preparation stage
The objective of this stage is to develop the manufacturing techniques and establish test market validity of the new product.
Selecting manufacturing procedures, production tools and technology, installation and start-up plans for the manufacturing process, and
Selecting vendors for purchased materials, components, and subsystems.
 Reproduction prototypes

41. Full-scale production stage
Final design drawings, specifications, flow charts, and procedures are completed for manufacture and assembly of all components and subsystems of the product, as well as for the production facility.
Quality control procedures and reliability standards are established
Contracts made with suppliers
Procedures established for product distribution and support.
Manufacturing facilities are constructed
Continuous process improvement (kaizen)

42. Product support stage
Technical manuals for product installation, operation, and maintenance
Training programs for customer personnel
Technical supports
Warranty services
Repair parts and replacement consumables must be manufactured and distributed
New procedures for operation and maintenance
Improved parts for retrofit
Notification of product recall for safety reasons

43. Disposal stage
Every product causes waste during manufacture, while in use, and at the end of useful life that can create disposal problems.
The time to begin asking, "how do we get rid of this" is in the early stages of product or process design.

44. CONCURRENT ENGINEERING AND CALS

45. Traditional Product Development
System Level Design
Subsystem Design
Component Design
Manufacturing Process Concept Development
Manufacturing Process Development
Delivery Development
Service Development
Delivery

46. Concurrent Processes System Level Design Subsystem Design
Component Design
Manufacturing Process Concept Development
Manufacturing Process Development
Delivery Development
Service Development
Delivery

47. Definition of Concurrent Engineering
A systematic approach to the integrated, concurrent design of products and their related processes, including manufacture and support.
This approach is intended to cause the developer, from the outset, to consider all elements of the product lifecycle from concept through disposal, including quality control, cost, scheduling, user requirements. (Inst. For Defense Analysis)

48. Advantages of Concurrent Engineering
The set of methods, techniques, and practices that:
Cause significant consideration within the design phases of factors from later in the life cycle;
Produce, along with the product design, the design of processes to be employed later in the life of the product;
Facilitate the reduction of the time required to translate the design into distributed products; and
Enhance the ability of products to satisfy users' expectations and needs.

49. CALS "Computer Aided Logistics Support," then
"Computer-aided Acquisition and Logistics Support,"
"Continuous Acquisition and Life-Cycle Support," (1993, DoD)
"Commerce At Light Speed" (U.S. industry)

50. Purposes of CALS
To enable more effective generation, management, and use of digital data supporting the life cycle of a product through the use of international standards, business process change, and advanced technology application.

51. CALS Electronic storage, transmission, and retrieval of digital data
Between engineers representing the several design stages,
Between organization functions such as marketing, design, manufacturing, and product support, and
Between cooperating organizations such as customer and supplier.

52. Commercial standards
Computer Graphics Metafile (CGM) (ISO-8632): A standard means of representing line drawings in a device-independent way.
Electronic Data Interchange for Administration, Commerce, and Transport (EDIFACT) (ISO 9735, ANSI X12): An international standard means for communicating commercial (trade) information.
Initial Graphics Exchange Specification (IGES) (ANSI Y14.26M): A standard means of representing product data in a device-independent way.

53. CONTROL SYSTEMS IN DESIGN
Drawing/Design Release
Configuration (Design Criteria) Management
Functional baseline (at end of conceptual stage)
Allocated baseline (at end of validation stage)
Product baseline (at end of development stage)
Design Review

54. PRODUCT LIABILITY & SAFETY
Caveat emptor (let the buyer beware)
“Privity of contract” (Direct contractual relationship)
1916, MacPherson v. Buick (No need for direct contract)
Plaintiff must prove negligence
1960, Hernington v. Bloomfield Motors,  implied warranty
1984, Greenman v. Yuba Power Product Strict Liability
Absolute liability: “A manufacturer could be held strictly liable for failure to warn of a product hazard, even if the hazard was scientifically unknowable at the time of the manufacture and sale of the product.”

55. Reducing Liability
Include safety as a primary specification for product design.
Use standard, proven materials and components.
Subject the design to thorough analysis and testing.
Employ a formal design review process in which safety is emphasized.
Specify proven manufacturing methods.
Assure an effective, independent quality control and inspection process.
Be sure that there are warning labels on the product where necessary.

56. Reducing Liability
Supply clear and unambiguous instructions for installation and use.
Establish a traceable system of distribution, with warranty cards, against the possibility of product recall.
Institute an effective failure reporting and analysis system, with timely redesign and retrofit as appropriate.
Document all product safety precautions, actions, and decisions through the product life cycle.

57. DESIGNING FOR RELIABILITY
Definition of Reliability:
Reliability is the probability that a system
Will demonstrate specified performance
For a stated period of time
When operated under specified conditions.

58. Reliability Measures Reliability R(t)=St /S0
Failure CDF (cumulative distribution function): F(t)=0t F / S0
Failure PDF (probability density function):
f(t) = Ft /S0
Failure or hazard rate: (t)= Ft /St

59. Simple Reliability Models
Series model
Parallel model
Series- parallel model
Bathtub curve

60. Designing for Reliability
“Start with the best”
Redundancy
Factor of safety

61. Maintainability
Maintainability is the probability that a failed system
Will be restored to specified performance
Within a stated period of time
When maintained under specified conditions.

62. Maintainability Maintenance downtime Administrative & preparation time
Logistic time
Active maintenance time
Types of Maintenance
Corrective maintenance
Preventive maintenance
Predictive maintenance

63. Availability
Inherent Availability (considers only corrective maintenance)
Ai = MTBF / (MTBF+MTTR)
Operational Availability (considers both preventive & corrective maintenance)
Ao = MTBM / (MTBM+MDT)
MTBM: Mean Time Between Maintenance
MDT: Mean Down Time
MTTR: Mean Time To Repair
MTBF: Mean Time Between Failure (1/)
BIT: Build-In Test

64. Other Considerations Human Factors Engineering (Ergonomics)
Standardization
Set of specifications for parts, materials, or processes intended to achieve uniformity, efficiency, and a specified quality.
Producibility

65. Value Engineering
A methodical study of all components of a product in order to discover and eliminate unnecessary costs over the product life cycle without interfering with the effectiveness of the product.
What is it?
What does it do?
What does it cost?
What does it worth?
What else might do the job?
What do the alternatives cost?
Which alternative is least expensive?
Will the alternative meet the requirements?
What is needed to implement the alternative?