Presentation on theme: "Design Tools 1 William Oakes, P.E Director of EPICS"— Presentation transcript:
1 Design Tools 1 William Oakes, P.E Director of EPICS Assoc. Prof. Engineering Education
2 Learning Objectives At the end of this session, you will be able to: Describe a specificationDescribe a decision matrixCategorize potential failures for a designPerform a functional decompositionCreate a personna
3 EPICS Balance Service Learning Service-learning is a balance of the learning of design and the service we contribute the communities through completed designs and supportServiceTo our partners, meeting needs in the communityLearningBecoming good designers, professionals & active citizensComplimentary goals that enhance each other
5 Specifications Development What does your project partner need?Don’t just rely on what they want, find out what they needUnderstand the problems and issues you are addressingWho will use product and who will benefit from it?Gather DataTalk to Project Partner and others impacted by the projectHow will the problem be worked?Criteria for design teamsHow will teams be integratedTransition plans for multiple semestersGather input from project partner on specificationsDevelop a specifications document and share it
7 Customer Requirements For a cell phone, make a list of Ten customer requirements
8 Design Specifications Answers the “how” questionQuantifiedShould be able to measure whether you meet itObjective quantitiesA set of units should be associated with each specificationForms the basis for your specifications document
9 Design RequirementsStarting with the customer requirements for a cell phone, make a list of design requirements
10 Defining Requirements BenchmarksWhat is availableWhy did they use their approachPatent searchesavoid infringementProtect IPAre we smarter than everyone else?Or did we miss something?
11 Design Targets Set standards to meet with your design How good is good Can be a living documentDon’t compromise on goals, but refine as the design progressesTool make design trade offsDesign decisionsCommunication with project partner
12 Decision Matrix Table with alternatives Quantify categories and score alternativesImportance in different categoriesUse judgement to do reality checksLeaves documentation of thought process of designCan be shared in design reviews
13 Criteria for Comparison Decision MatrixIdeas to be comparedCriteria for ComparisonWeightsScoresTotals
16 Functional Decomposition Breaking tasks or functions of the system down to the finest levelCreate a tree diagram starting at the most general function of your systemWhat is the purpose of your system?Break this function down into simpler subtasks or subfunctionsContinue until you are at the most basic functions or tasks
18 Sample Diagram – Bike Fender Protect rider from water and dirt off wheelShield riderSteer water away from riderAttach Splashguard
19 Functional Decomposition Each function has a box withAn action verbThe object(s) on which the verb actsPossibly a modifier giving details of the functionKnown flows of materials, energy, control or informationConsider WHAT not HOW
20 Create a functional decomposition diagram for a mechanical pencil Prepare them to share
22 DFMEA Steps Review the design Brainstorm potential failure modes List potential effects of failureRank failuresSeverityOccurrenceDetectionRPN = Severity X Occurrence X DetectionDevelop action planImplement fixesRevisit potential failure risks
23 Describe the project so the whole group understands it In a group, Identify one project to use as an example for this exerciseDescribe the project so the whole group understands it
24 Brainstorm Failures What could go wrong? What could break? Are there systems your design relies upon?e.g. myEPICS software authenticates through Purdue’s career accounts. What if the server goes down?Are there things that could fail over time?
25 Brainstorm a list of potential failures for the project
26 Rate failures Severity Occurrence Detection Rating (1 to 10) How severe are the consequences to the failureOccurrenceHow often are the failures likely to occur?DetectionHow easily are the failures detected?
27 DFMEA Calculations Scores for Severity, Occurrence and Detection 1 to 101 = Low10 = HighRisk Priority Number (RPN)RPN =Severity X Occurrence X Detection
31 Identify the failure scenario that should be addressed first
32 Develop an action plan to address the failure scenario
33 Continue the processImplement the plan to eliminate the failure scenarioRevisit other potential failure risksPrioritizeEliminate failure scenariosContinue until risks are below determined thresholdsShow to the design reviews for confirmation
Your consent to our cookies if you continue to use this website.