1 / 29

Engineering Design

Engineering Design. Brief Case Study: What is the Engineering Design Process and Why is it Critical? Rochester Institute of Technology Mechanical Engineering Department Rochester, NY USA. Questions…. Session Objectives. Design process overview Problem statement Voice of the Customer

ddugan
Télécharger la présentation

Engineering Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Engineering Design Brief Case Study: What is the Engineering Design Process and Why is it Critical? Rochester Institute of Technology Mechanical Engineering Department Rochester, NY USA

  2. Questions…

  3. Session Objectives • Design process overview • Problem statement • Voice of the Customer • Voice of the Engineer • Generate and Select Concept

  4. Session Objectives • Design process overview • Problem statement • Voice of the Customer • Voice of the Engineer • Generate and Select Concept

  5. Design Process(Ulrich & Eppinger Exhibit 2-2) • Phase 0: Planning • Phase 1: Concept Development • Phase 2: System-Level Design • Phase 3: Detail Design • Phase 4: Testing and Refinement • Phase 5: Production Ramp-Up DPM MSD I MSD II

  6. Planning (U&E) • Doing this now! • Identify market opportunities • Consider product platform and architecture • Assess new technologies • Research available technologies • Identify production constraints

  7. Concept Development (U&E) • Identify Customer Needs • Establish Target Specifications • Generate Product Concepts • Select Product Concepts • Test Product Concepts • Set Final Specifications

  8. Session Objectives • Design process overview • Problem statement • Voice of the Customer • Voice of the Engineer • Generate and Select Concept

  9. “We need a better ladder” • Take 2 minutes and design a better ladder.

  10. Read handout • What’s changed…?

  11. Session Objectives • Design process overview • Problem statement • Voice of the Customer • Voice of the Engineer • Generate and Select Concept

  12. Read handout • What’s changed…? • Customer/market • Can capture the Voice of the Customer • Take 4 minutes • Write a set of 4-5 customer needs for your client. • Prepare a brief statement to the class: describe customer and needs.

  13. “We need a better ladder” • Take 2 minutes and design a better ladder

  14. Was this easier? • Hopefully yes! • Can we do better? Yes!

  15. ---Break--- • Take 10 minutes and come back for the Voice of the Engineer

  16. Session Objectives • Design process overview • Problem statement • Voice of the Customer • Voice of the Engineer • Generate and Select Concept

  17. Voice of the Engineer • Functional decomposition: • What functions does the product/process need to perform? • What constraints are present? • Core function of a ladder (all scenarios)? • Ask, “How is the device going to do that?”

  18. Function Tree • Take 5 minutes and come up with a list of functions that YOUR ladder needs to perform • Function is an active statement: verb-noun • Note: We will spend more time on this in class, so don’t worry if it’s not perfect today!

  19. Metrics and Specifications • How are you going to measure how well those functions are performed? (Metric) • What is your threshold for success? (Specification) • These require feasibility analysis

  20. Session Objectives • Design process overview • Problem statement • Voice of the Customer • Voice of the Engineer • Generate and Select Concept

  21. Concept Generation • Take 2 minutes: each team member brainstorm how to perform a single function on your ladder’s function tree • Ex: 5 team members can develop ideas for 5 functions • The process has provided structure for solving your problem – this should be much easier!

  22. Morphological Chart • A tool that will allow you to assemble complete system ideas from your list of function concepts. • More on this later…

  23. Means Functions

  24. Design a Better Ladder • These system concepts are ideas for better ladders.

  25. Concept Selection • Take 2 minutes and decide which concept is the best • What was your team’s process?

  26. Selection Criteria • Evaluate each system concept against a predetermined set of criteria • Objective, not subjective • May require some feasibility analysis • Allows you to look at the good and bad of each system, and iterate and improve on your ideas • You will not do a complete concept selection in DPM!

  27. Hand-Off from DPM to MSD • You are now delivering a well-thought-out project. • You know there are feasible solutions • You have reviewed the customer needs and specifications • You are more confident that you are solving the correct problem.

  28. Design Process(Ulrich & Eppinger Exhibit 2-2) • Phase 0: Planning • Phase 1: Concept Development • Phase 2: System-Level Design • Phase 3: Detail Design • Phase 4: Testing and Refinement • Phase 5: Production Ramp-Up

  29. Questions?

More Related