Design Tools 1 William Oakes. Learning Objectives At the end of this session, you will be able to: 1.Describe a decision matrix 2.Categorize potential.

Slides:



Advertisements
Similar presentations
Quality Planning Tools PMI Westchester Quality SIG Pawan Kumar, Quality SIG Member, PMP November 2007.
Advertisements

STEM Project Design Science Technology Engineering and Math STEM Service-Learning Summer institute Sacramento State University August 5-7, 2009.
Design Tools 1 William Oakes, P.E Director of EPICS
PROJECT RISK MANAGEMENT
Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
How to Map a Sales Process That Creates Value for Customers! July 2003.
Formulate Alternatives. Accomplishments n Put together a team n Established a shared vision of the status quo n Identified problems n Defined planning.
Project Management.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Chapter 7: Managing Risk
Introduction to Engineering Design
Teaching Design William Oakes. Learning Objectives At the end of this session, you will be able to: 1.Describe design 2.List at least three steps in the.
1 Human-Centered Design I Presented by: Craig Titus EPICS High Workshop – Summer 2010 Lecture: Human-Centered Design Presented By: Craig Titus.
Teaching Design William Oakes. Learning Objectives At the end of this session, you will be able to: 1.Describe design 2.List at least three steps in the.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Auditing A Risk-Based Approach To Conducting A Quality Audit
Systems Analysis and Design: The Big Picture
4.1 EbD Human-Centered Design 1 ® ®. Essential Question: ® How can the Human-Centered design model help frame my project and how will all the information.
System design technique  System Development Life Cycle  Prototyping  Rapid Application Development.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Logic and Problem Solving Advanced Computer Programming.
Quality Function Deployment
CPSC 871 John D. McGregor Module 4 Session 3 Architecture Evaluation.
Washington State Teacher and Principal Evaluation 1.
Chapter 7 Business Process Redesign Reference: Tan, A. (2007). Business Process Reengineering in Asia: A Practical Approach, Pearson Education, Singapore.
Managing Risk. Objectives  To Describe Risk Management concepts and techniques  To calculate and analyze a project using Probability of completion 
3.5 EbD Reflection on Service- Learning 1 ® ®. Essential Question: ® How can I organize the information I have gathered to create a project that will.
TQM TECHNIQUES BENCHMARKING Target key areas for improvement within operations – Increase productivity, competitiveness, and quality – Quality results.
A Cleaner Production Project in the South African Paper Industry – Lessons learnt Iain Kerr, MSc (Env. Biotech.) University of KwaZulu Natal, School of.
Root Cause Tutorial Page 1 More on Hazard Identification Techniques 1.Identify potential hazards that could threaten the safety of your employees,
Tingxuan Liu Risk Management in Software engineering.
© 2014 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license.
Integrated Risk Management Charles Yoe, PhD Institute for Water Resources 2009.
CVE 4070 Construction Engineering Value Engineering Prof. Ralph V. Locurcio, PE.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Communicating Impact Elizabeth Coke Haller School Health Team Leader Program Development and Services Branch Division of Adolescent and School Health.
Product Design and Development
EPICS Design Process. Design Process and Project Mgt Many models and tools Design Process oMechanical Engineering Ullman’s - 6 steps oEngineering Your.
Managing Risk CHAPTER SEVEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Collaborative Problem Solving
Project & Risk Management
District Leadership Module Preview This PowerPoint provides a sample of the District Leadership Module PowerPoint. The actual Overview PowerPoint is 73.
OVERVIEW OF TOOLS & TECHNIQUES: GREEN PRODUCTIVITY R. C. Monga 2nd World Conference on Green Productivity 10 December 2002.
US Army Corps of Engineers BUILDING STRONG ® Overview of Risk Approach to Manage USACE Dam and Levee Safety Program The Reality of Risk: Dam Safety in.
1 Project Management C53PM Session 3 Russell Taylor Staff Work-base – 1 st Floor
Problem Solving Skills
John D. McGregor Architecture Evaluation
Root Cause Analysis Analyze Kaizen Facilitation. Objectives Learn and be able to apply a fishbone diagram Utilize “Why” analysis technique to uncover.
1 Introduction to Design I Presented by: Dr. Carla Zoltowski Find a partner for today’s lecture. Professional Development Series Lecture (Project Management:
Switch off your Mobiles Phones or Change Profile to Silent Mode.
UNIT III. A managerial problem can be described as the gap between a given current state of affairs and a future desired state. Problem solving may then.
1 CONCEPTUAL DESIGN PHASE 1.Specification Development / Planning Phase Determine need, customer and engineering requirements Develop a project plan 2.Conceptual.
Failure Modes, Effects and Criticality Analysis
Concept Selection and DFMEA Heidi Ploeg Associate Professor Mechanical Engineering and Biomedical Engineering.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
The Information Systems Development Processes Chapter 9.
Six Sigma Greenbelt Training
Failure Mode & Effect Analysis (FMEA)
Quality Function Deployment
Ranjan kumar Assistant Manager CCL,Ranchi
PROBLEM SOLVING June 2010 CANADIAN COAST GUARD AUXILIARY - PACIFIC.
FMEA.
Improvement Selection:
Value Management.
MINGGU KE 9: PROSES DESAIN PRODUK BARU
Tools for Implementation
Tools for Implementation
PFMEA Summary Process Steps
HRA: Aerospace Challenges
Presentation transcript:

Design Tools 1 William Oakes

Learning Objectives At the end of this session, you will be able to: 1.Describe a decision matrix 2.Categorize potential failures for a design 3.Perform a functional decomposition

EPICS Balance Service-learning is a balance of the learning of design and the service we contribute the communities through completed designs and support Service To our partners, meeting needs in the community Learning Becoming good designers, professionals & active citizens Complimentary goals that enhance each other

Design Tool: Engineering specifications

Specifications Development What does your project partner need? oDon’t just rely on what they want, find out what they need oUnderstand the problems and issues you are addressing oWho will use product and who will benefit from it? Gather Data oTalk to Project Partner and others impacted by the project How will the problem be worked? oCriteria for design teams oHow will teams be integrated oTransition plans for multiple semesters Gather input from project partner on specifications oDevelop a specifications document and share it

Customer Requirements Types of customer requirements oFunctional performance oHuman factors oPhysical oTime (reliability) oCost oStandards oTest Method oService & maintenance

Customer Requirements For a cell phone, make a list of Ten customer requirements

Engineering Specifications Answers the “how” question Quantified oShould be able to measure whether you meet it Objective quantities A set of units should be associated with each specification Forms the basis for your specifications document

Engineering Requirements Starting with the customer requirements for a cell phone, make a list of engineering requirements

Defining Requirements Benchmarks oWhat is available oWhy did they use their approach oPatent searches avoid infringement Protect IP Are we smarter than everyone else? oOr did we miss something?

Design Targets Set standards to meet with your design How good is good Can be a living document oDon’t compromise on goals, but refine as the design progresses Tool make design trade offs oDesign decisions oCommunication with project partner

Design Tool: Defining the System

The EPICS Design Cycle Specification Development Detailed Design Production Service Maintenance Redesign Retirement Problem Identification Conceptual Design Disposal

Functional Decomposition Breaking tasks or functions of the system down to the finest level Create a tree diagram starting at the most general function of your system oWhat is the purpose of your system? Break this function down into simpler subtasks or subfunctions Continue until you are at the most basic functions or tasks

Functional Decomposition Diagram Overall Function Subfunction 1 Subfunction 2 Subfunction 3

Sample Diagram – Bike Fender Protect rider from water and dirt off wheel Shield rider Steer water away from rider Attach Splashguard

Functional Decomposition Each function has a box with oAn action verb oThe object(s) on which the verb acts oPossibly a modifier giving details of the function oKnown flows of materials, energy, control or information Consider WHAT not HOW

Create a functional decomposition diagram for a mechanical pencil Prepare them to share

Generating Ideas - Brainstorming 1.Pick A Facilitator 2.Define The Problem 3.Small Group 4.Explain the Process 5.Record Ideas in a Visible Way 6.Everyone’s Involved 7.No Evaluating 8.Eliminate Duplicates 9.Pick Three

In the same group Brainstorm ways to implement one of the functions on your diagram and select the best alternative Prepare it to share

Decision Matrix Table with alternatives Quantify categories and score alternatives oImportance in different categories Use judgement to do reality checks Leaves documentation of thought process of design oCan be shared in design reviews

Decision Matrix Ideas to be compared Criteria for Comparison Weights Scores Totals

Decision Matrix Example: Getting a Job CriteriaWtsCo. ACo. BCo. CCo. D Location5 Salary4 Bonus2 Job3 Training2 Boss2 Totals

DFMEA : Design for Robustness

Design Phase: Testing for Failures Planning to avoid failures Disposal Specification Development Detailed Design Production Service Maintenance Redesign Retirement Problem Identification Conceptual Design

DFMEA Steps 1.Review the design 2.Brainstorm potential failure modes 3.List potential effects of failure 4.Rank failures a)Severity b)Occurrence c)Detection 5.Develop action plan 6.Implement fixes 7.Revisit potential failure risks

In a group, Identify one project to use as an example for this exercise Describe the project so the whole group understands it

Brainstorm Failures What could go wrong? What could break? Are there systems your design relies upon? oe.g. myEPICS authenticates through Purdue’s career accounts Are there things that could fail over time?

Brainstorm a list of potential failures for the project

Rate failures Rating Severity How severe are the consequences to the failure Occurrence How often are the failures likely to occur? Detection How easily are the failures detected?

DFMEA Matrix Failure modeSeverityOccurrenceDetectionRating

Identify the failure scenario that should be addressed first

Develop an action plan to address the failure scenario

Continue the process Implement the plan to eliminate the failure scenario Revisit other potential failure risks oPrioritize oEliminate failure scenarios Continue until risks are below determined thresholds oShow to the design reviews for confirmation

Questions/Discussion