1. ME 4054W: Design Projects RISK MANAGEMENT

2. 2 Lecture Topics What is risk? Types of risk Risk assessment and management techniques

3. 3 Risk Trivia The study of risk as a science started during the Renaissance in the 16 th century. The initial impetus was from the financial world. The word “risk” is derived from the early Italian word “risicare” which means “to dare”.

4. 4 Risk Risk is a measure of the probability and severity of adverse effects. 1 1 Lowrance 1976 Risk involves the possibility of loss. Without the potential for loss, there is no risk. Managing risk involves choice. Without choice, there is no risk management.

5. 5 Risk Risks are future events with a probability of occurrence and a potential for loss. If caught in time, risks can be avoided or have their impacts reduced. Completely eliminating all risk would be very expensive, if not impossible. The key is achieving an acceptable risk level.

6. 6 What are some of the types of risk found in projects?

7. 7 Types of Risk Found in Projects Technology risk Economic risk Market risk Timing risk etc. Human resource risk Operational risk Geographic risk Environmental risk The primary focus of the balance of this lecture will be technology risk

8. 8 Team Exercise What are some items on your project that you consider risks? What are some of the attributes of the items identified as risks?

9. 9 Risk Assessment Kaplan and Garrick 1981 It is common in risk assessment processes to seek answers to the following set of questions: What can go wrong? What is the likelihood that it would go wrong? What are the consequences?

10. 10 What is Risk Management? businessdictionary.com The identification, analysis, assessment, control, and avoidance, minimization, or elimination of unacceptable risks. Identify, assess, prioritize, then manage risk.

11. 11 Risk Management Haimes 1991 Risk management seeks to answer a second set of three questions: 1.What can be done and what options are available? 2.What are the associated tradeoffs in terms of all costs, benefits, and risks? 3.What are the impacts of current management decisions on future options?

12. 12 Risk Management When should it be done? –Recommended practice is to apply risk management before “release” using judgment, expert knowledge and experience. –Risk should also be monitored throughout a product’s life. –Not all issues are identified before the fact. Analyzing and responding to failures is an important aspect of risk management.

13. 13 Failure Mode & Effects Analysis (FMEA) FMEA is a structured approach aimed at identifying all possible failures in a design, process, product or service. It is also called potential failure modes and effects analysis (PFMEA) and failure modes, effects and criticality analysis (FMECA). Source: American Society for Quality (asq.org)

14. 14 Failure Mode & Effects Analysis (FMEA) “Failure modes” means the ways, or modes, in which something might fail. Failures are any errors or defects, especially ones that affect the customer. Failures can be potential or actual. “Effects analysis” refers to studying the consequences of those failures. Source: American Society for Quality (asq.org)

15. 15 Failure Mode & Effects Analysis (FMEA) The purpose of the FMEA is to take actions to eliminate or reduce failures, starting with those that are the highest priority. Ideally, the use of FMEA begins during the earliest conceptual stages of design and continues throughout the life of the product or service. Source: American Society for Quality (asq.org)

16. 16 Failure Mode & Effects Analysis (FMEA) When to use FMEA When a process, product or service is being designed or redesigned, after quality function deployment. When an existing process, product or service is being applied in a new way. Before developing control plans for a new or modified process. Source: American Society for Quality (asq.org)

17. 17 Failure Mode & Effects Analysis (FMEA) When to use FMEA When improvement goals are planned for an existing process, product or service. When analyzing failures of an existing process, product or service. Periodically throughout the life of the process, product or service. Source: American Society for Quality (asq.org)

18. 18 FMEA Procedure 1.Assemble a cross-functional team with diverse knowledge about the process, product or service and customer needs. Functions often included are: design, manufacturing, quality, testing, reliability, maintenance, purchasing, sales, marketing and customer service. Suppliers and customers can be added, if needed, to supplement the team. Source: American Society for Quality (asq.org)

19. 19 FMEA Procedure 2.Identify the scope of the FMEA. Is it for a concept, system, design, process or service? What are the boundaries? How detailed should we be? Source: American Society for Quality (asq.org)

20. 20 FMEA Procedure 3.Complete the FMEA form beginning with the identifying information at the top of the form. Source: American Society for Quality (asq.org)

21. 21 FMEA Procedure In an FMEA, potential failure modes are rated on the following attributes: –Severity (S) is an assessment of the severity of the potential effect of the failure. –Occurrence (O) is an assessment of the likelihood of occurrence of the failure. –Detection (D) is an assessment of the likelihood that the problem will be detected before it reaches the end-user/customer.

22. 22

23. 23

24. 24

25. 25 FMEA “By The Numbers” The Risk Priority Number (RPN) is defined as: RPN = S x O x D The Criticality Index (CI) is defined as: CI = S x O

26. 26 FMEA “By The Numbers” RPN and CI are used to assess the risk associated with potential problems in a product or process design and to prioritize issues for corrective action. The RPN or CI values that require action are project/product-specific. An approximate rule of thumb is if RPN ≥ 200 or CI ≥ 40, then that risk should be mitigated. All risks with severity of 10 must be mitigated.

27. 27 Simple FMEA Example Source: American Society for Quality (asq.org)

28. 28 “Completing” the FMEA Use the RPN and CI to set priorities for corrective actions. Assign responsibilities and target completion dates for the corrective actions. After action is taken, reassess S, O and D and recalculate RPN and CI to determine if additional actions are needed.

29. 29 Risk Management Decision Making The graphic at right provides a general guideline for decisions about when to mitigate risks. There is no single right answer; a number of similar guideline tables exist. It is strongly suggested to err on the side of caution. Green = No mitigation needed Yellow = Consider mitigating risk Red = Risk mitigation needed

30. 30 You’ve launched the product and there are failures. What now? The FMEA process is primarily focused on pre-release risk management, but can be used after launch. Many other processes, such as FRACAS, Fault Tree Analysis, Root Cause Analysis and 5 Whys are available to assess and manage failures of commercial products.

31. 31 FRACAS FRACAS stands for Failure Reporting and Corrective Action System. FRACAS provides a process for reporting, classifying, analyzing failures, and planning corrective actions in response to those failures. Common FRACAS outputs may include: Field MTBF, MTBR, MTTR, spares consumption and reliability growth.

32. 32 Sample FRACAS Process Flow http://www.maintenancephoenix.com/wp-content/uploads/2013/01/FRACAS-MTBF-Process-Map.jpg

33. 33 Root Cause Analysis Root cause analysis (RCA) is a method of problem solving that tries to solve problems by attempting to identify and correct the root causes of events, as opposed to simply addressing their symptoms. Focusing correction on root causes has the goal of preventing problem recurrence.

34. 34 http://withfriendship.com/images/f/25154/a-root-cause-analysis-is.gif

35. 35 Fault Tree Analysis Fault tree analysis (FTA) is a top down, deductive failure analysis in which an undesired state of a system is analyzed using Boolean logic to combine a series of lower-level events.

36. 36 5 Whys The 5 Whys is an iterative question-asking technique used to explore the cause-and- effect relationships underlying a particular problem. The primary goal is to determine the root cause of a defect or problem.

37. 37 5 Whys Example The vehicle will not start. (the problem) o Why? - The battery is dead. (first why) o Why? - The alternator is not functioning. (second why) o Why? - The alternator belt has broken. (third why) o Why? - The alternator belt was well beyond its useful service life and not replaced. (fourth why) o Why? - The vehicle was not maintained according to the recommended service schedule. (fifth why, a root cause) A possible corrective action addressing the fifth Why and solution to the problem’s root cause is to maintain the vehicle according to the recommended service schedule. Adapted from http://en.wikipedia.org/wiki/5_Whys

38. 38 Risk Management Cycle